Le 16/04/12 14:49, Mark Stanton a écrit :
Hi Mark,
- multiple table query/update support
Multi-tabe query is available, surely? Where it's not available is in
file mode when there's no backing database engine. Or having I missed
somthing?
Multi-table update support is an SQL limitation, isn't it?
Sorry, I should have been more precise :
Lotus Approach allowed a user to create a form based on a query of a
collection of DBF tables and then be able to update them via the form
(or an update statement) - of course, relationships/foreign keys needed
to be involved, but it did work. This was a particular plus point over
the single flatfile driver that we have always had with OOo and now LO.
In other words, it allowed for updates/writes to cross-table flatfiles
as far as I can recall. You can not do this with the flatfile driver of
LO - only a single DBF file can be updated/written to at one time, and
as for Calc or Excel, well they are just read only datasources within
the framework of Base.
I don't know how Lotus/IBM did this, but it was a very, very, neat feature.
Alex
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.