I'm unsure of the practical implications of the difference between Base
implementation of Views and Queries. Perhaps someone can enlighten me.
One thing, however, does hit me.
Views will be executed in the database. The content will look for Base
like a non-writable table. You could filter data, sort data and use this
views for repprts, but you couldn't update, add or delete data.
Database won#t know anything about queries in the queries pane. Queries
will send from tBase to the database. So queries will be a little bit
slower. But queries could be used for input, update or delete data, if
all primary keys of the included tables were available.
Initial design of a View with the GUI, is done similar to a Query,
which is OK. However, when the View is stored, then further development
of that View seems very limited if not impossible, as the Table-type
GUI is opened on Edit.
Which version pf LO and which (internal) database do you use? This bug
(opening table editor, not query editor) has been solved for internal
Firebird database some times ago. In LO 22.214.171.124 the query editor will
One hint: I will save all views separately as queries. It is because a
view could depend on another view. So I couldn't chang the view I first
created, if another view needs data of this view. I have to delete other
views depending on this view and have to recreate them afterwards.
To unsubscribe e-mail to: firstname.lastname@example.org
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Impressum (Legal Info)
: 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