Am 17.04.2012 11:34, ptoye wrote:
Andreas Säger wrote
Why can't you run SQL update queries? This is trivial to do in SQL. The
SQL is trivial to execute by macro.
If you desparately want a graphical query designer for
update/insert/delete queries, then you should write one and store your
queries somewhere in the .odb container.
Of course I can. If I can find out how to do it.
But this isn't the point, is it? The real point is that database front-ends
and macro languages are meant to make life easy, not difficult. You seem to
dislike "sugar" - worried about your diameter? The computer was made for
man, not man for the computer. Why not program in assembler - gives you much
more control and isn't really that hard (I speak from years of assembler
experience and with my tongue firmly in my cheek)?
You get what you pay for. The rest is about community. Unfortunately,
this office suite has more consumers and complainers than contributors.
Regarding your remark on assembler code: A very high software stack
imposes a new quality of problems that would be unknown on hardware level.
Fortunately, there is still the OpenOffice.org community:
(which could be even more useful if someone would rewrite these Basic
routines as a true extension of UNO-components)
For unsubscribe instructions e-mail to: firstname.lastname@example.org
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
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