I list some of the draw-backs in the linked response to your challenge.
http://user.services.openoffice.org/en/forum/viewtopic.php?f=61&t=6025&p=53756#p53756
Regarding the example databases you mention without linking them, no I
don't know. Regarding macros we have the same problem as with VBA. You
can not reproduce the features unless you can read and write code or,
even worse, German. What are you all hacking upon? This API is full of
holes.
Does parameter substitution work after all the years since v2.0?
Do you remember your own CopyRow macro in
http://user.services.openoffice.org/en/forum/viewtopic.php?f=45&t=1169 ?
It still overwrites existing records unless I move to the last row
before moving to the insert row.
How many tries and errors did we follow in the forums before someone
found a reliable method to open a form/report on button-click?
I have tons of Base related macro-snippets, but I lost confidence that
all this can be used transparently in a generic manner without
re-writing and adjusting for every single use case. This *playground* is
nothing but a huge waste of time. I can't use it for my own purposes[*]
and I can't earn my living building Base databases like I could with my
very first Access projects back in 1999. One of the databases was
presentable within one day. The most difficult problems I remember were
the layouts, logos, fonts, corporate background colors, pictures and
other visual requirements.
Have you ever seen "Northwind.mdb" working in MS Access? Did you notice
that the whole database has almost no dispatch-macros nor VBA?
[*] I use to use the very same flat dBase file with input in data source
window and data pilots as reports since version 1.1.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
