Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Have a nice day, Jay!


planas <jslozier <at> gmail.com> writes:


Hi Vladimir,

...

Is it possible to change the way of LO making relation's query or to
find an another way to solve my problem?

Thank you in advance!

P.S. I have no subscription to this mailing list so send your answers
to my address too, please!

-- 
Sincerelly yours,
Vladimir G. Drobyshevsky
Wanna call me? Do it right now: +7 912 2473415


My limited experience with SQL suggests you should qualify the typeID
fields to remove any ambiguity. I have had this problem when working
directly the outside database and developing queries for it. If one did
properly qualify the ambiguous fields you get a similar error message.


Thank you for answer!

You absolutelly right in your sugesstion, but WHERE clause is changed
automatically (by adding 'AND "typeID" = :link_from_ProductID' ) by LO, as I
wrote above. I would be very grateful if you can show me solution to change it.

-- 
Sincerelly yours,
Vladimir G. Drobyshevsky
Wanna call me? Do it right now: +7 912 2473415


-- 
Unsubscribe instructions: E-mail to users+help@global.libreoffice.org
In case of problems unsubscribing, write to postmaster@documentfoundation.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

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.