Actually, goApp.mFilterVisibility() would be a much cleaner solution as it would get the latest state of the filter chosen by the user.
Are you saying it would NOT try to execute it once per record handled in the SQL statement (and therefore slow things down)? That was my initial fear. My data set is to small to gauge a slowdown myself. Thx Henry -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Tracy Pearson Sent: 2009-04-02 2:44 PM To: [email protected] Subject: RE: Macro Substitution using object/property in SQL Henry To work around that you need to macro the sql statement as a whole. tmpSQL = "SELECT ... AND " + goApp.cFilterVisibility &tmpSQL. The drawback is if you change cFilterVisibility after it doesn't update. Have you tried SELECT ... AND goApp.mFilterVisibility() Where goApp.mFilterVisibility returns THIS.cFilterVisibility Tracy -----Original Message----- From: [email protected] Sent: Thursday, April 02, 2009 2:42 PM Hi Tracy, Thanks for your reply. (goapp.cFilterVisibility) gives 'Function argument value, type...' As for x = goapp.cFilterVisibility and using &x, the problem is that x will not exist later when the view needs to be instantiated. Obviously, I could resort to PUBLIC vars but I've been avoiding those in favour of my 'goapp' global object. Thx Henry [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
