I don't recall if I've actually put this type of behavior into a test scenario. Perhaps someone else on the list has and could chime in.
Tracy -----Original Message----- From: [email protected] Sent: Thursday, April 02, 2009 3:01 PM 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 _______________________________________________ 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/000e01c9b3c5$54b72df0$fe2589...@com ** 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.
