This will definitely be a nice addition. I've written my own for now as an A4L function - it's an ugly-a$$ set of case statements but it works well. I found out about 4D not allowing the variable in the conjunction when writing my function (causing the function blowup big time). Also, just to note that for built queries they don't allow the variables for the '*' at the end of the multi-line queries, so had to handle that as well (causing another swelling of the function code).
-------------------------------- Steven R Abney CSS Group, Inc Applications Developer ________________________________________ From: [email protected] on behalf of Aparajita Fishman Sent: Friday, September 27, 2013 10:21 AM To: Active4D Developer Discussion List Subject: Re: [Active4d-dev] Oddness with Query extended format Hi, > I'm running into something odd when using the query extended format: > > QUERY/QUERY SELECTION(inTable; inConjunction; inField; inComparator; inValue > {;*}) > > For some reason, I cannot use a variable in place of inConjunction or > inComparator. However, 4D itself does allow variable usage with the extended > query format. This will be fixed in v6.1r2. Whereas 4D does not actually allow an expression for the conjunction, Active4D will allows a unary expression. Regards, Aparajita www.aparajitaworld.com "If you dare to fail, you are bound to succeed." - Sri Chinmoy | www.srichinmoy.org _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/ _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
