Hi Peter,
I have a query which works fine. But when I edited it in the graphical query> editor LO refused
to save it saying that there was an SQL error. The>
detailed message was "syntax error, unexpected $end, expecting BETWEEN
or IN> or SQL_TOKEN_LIKE". Even if I try to save the unedited version I
get the> error, which I find a bit bizarre. But it runs OK and gives the
correct> result.
This is the default-message when GUI doesn't know how to change the
code. You have designed the query after switchung from GUI to direct SQL
for adding
UCASE( "Wines"."Wine_Name" ) LIKE UCASE( '%' || ( SELECT "filterstring"
FROM "tblfilter" ) ) || '%'
and the query will work.
Could be better to change it a littel bit
UCASE( "Wines"."Wine_Name" ) LIKE '%' || UCASE( SELECT "filterstring"
FROM "tblfilter" ) || '%'
and to set the subquery for only one row, but could be it won't change
the behavior. Query will be opened for changing in GUI-Mode, but this
wouldn't work ...
Regards
Robert
--
Homepage: http://robert.familiegrosskopf.de
LibreOffice Community: http://robert.familiegrosskopf.de/map_3
--
To unsubscribe e-mail to: users+unsubscribe@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.