Hi Frank, I've been mostly unavaillable during the second half of December, so I could not drop in earlier. Somewhere in the above thread there was a notion about "ThisComponent" always beeing currently active Writer document and that this would collide with the location of code in a superordinate container document, which does not hold true.
Frank Schönheit - Sun Microsystems Germany wrote: > The concept by now is to let ThisComponent always refer to the context > from which the macro was invoked (a form/report, or even a query/table > designer), and have an additional ThisDatabaseDocument which refers to > the, well, database document in which the macro is embedded. > > Ciao > Frank > Well, I just wanted to point out that this has been so "ever since". Completely off-topic, just for the records and my personal relieve: I'm convinced that the current implementation of Base is the worst design flaw in this whole office suite. So much wasted development for a package format which deserves to be "installed" every time you open an *.odb file. 1. Embedded databases have been reported to lose data which is inacceptable. 2. Performance of embedded databases is too bad. 3. You can not create desktop-links to reports nor forms. You have to open the container and browse to the form or report you want to work with. 4. Far too many users do not understand the whole concept of embedded vs. linked data in a container format. They simply create a "document in Base format", connect to an existing set of tables (dBase, text, spreadsheet) and expect to get a fully functional database. Or they create a "native" one and end up in the middle of nowhere, even if they have some experience with Access. 5. There is no native documentation for the "native" type of databse. I don't accept http://hsqldb.org/web/hsqlDocsFrame.html as native documentation of OOo's native database format. 6. The query designer and various wizzards are the only GUI-tools. Currently there is no way to create Base-extensions. The query designer covers a tiny subset of possible selects in hsqldb, whereas all the other types of databases are nearly unsupported (select, distinct, where, order by, count(*), that's it). 7. Finally, embedded binary data has nothing to do with ODF. A single-file database has no advantage over connections if the overall concept and it's restrictions is that complex and difficult to understand. The old concept in versions 1.x allowed forms and reports of any type. Arbitrary documents could be linked to the datasource in the datasource pane. I prefer simple Calc reports (pivot tables and pretty formatted query imports). They can not be bundled with the current container format. Instead of fixing all that odb-mess it would be far more important to implement joins on dBase tables and a common set of stored procedures for any kind of table. Better support for dBase is crucial because it has been *the* format for simple databases and there is so much software supporting this format and on the forums there are many requests related to dBase. I see dbf in one line with doc, xls and ppt. If a redesign where possible at all, I would like to discuss another concept (yes, I believe in the term "impossible" for practival reasons). Assume an extensible set of tools to connect with various sources, based on the existing API. Users can create forms and reports in Writer/Calc and even Impress/Draw. The registration of databases includes the connection, queries, forms and reports. Just like it was in 1.x. There could be various extensions to create beautiful forms and reports and query-designers tailored to mySQL, hsql, postgre,... For a self-contained, fully featured and distributable database use JRE and hsql from which you can create an integrated database package. dBase and csv-packages should be possible as well. Of course there are a nice extensions to help you bundle your database distribution. On the target system you need OOo, JRE and hsql before you install the database-distribution with admin privileges. Your package registers the new hsqldb at the server, including all pre-defined groups and privileges, stored procedures, triggers and stuff. The package provides access to predefined queries, forms and reports. Forms and reports are office documents accessable through desktop-links datasource pane. Very much like the old datasources in OOo 1.x plus extensions. Just dreaming, Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
