If people decided to go the VBA way, they have to bear the consequences.
There is no drop-in replacement and there will _never_ be one [OK, 30
years from now in academic seminars on ancient APIs].
I wish there would be the old interfaces of version 1. You have a
database and a driver? Fine, so you already know what a database is,
create the required configuration entries and use the record sets in
Writer and Calc. You can even create input forms and macros if you like.
How silly to create an external configuration tree (a "Base document")
for this most frequently used puropose.
The old concept with some additional tools would have been far better
than a container format that needs to be worked-around most the time.
The Base container has only one advantage but too many disadvantages.
http://user.services.openoffice.org/en/forum/viewtopic.php?f=61&t=6025&p=53756#p53756
Many other products use or can use dBase. Thus dBase relations are
desparately missing. For portability of databases a simple tool to
create dBase add-ons with data, configuration, forms, reports and macros
would suffice.
Why can't we use some of the spreadsheet functions in SQL? Most of the
functions are callable in array-context (taking vectors and returning
vectors). Even the HSQL folks seem to be unhappy with Base. It does not
raise the reputation of their product.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
