And here's a use case where SET FILTER can be quite useful in a production application. Let's say you have a form that displays account receivable transactions for a customer (invoices, payments, adjustments, etc.). You want to be able to display only open (i.e. unpaid) transactions or transactions related to a specific invoice. The primary query has returned all the rows I need to display for that customer. SET FILTER handles that quickly and simply without the overhead of running another query against the main database.
-- rk -----Original Message----- From: ProfoxTech <[email protected]> On Behalf Of Gene Wirchenko Sent: Wednesday, May 15, 2019 2:55 PM To: [email protected] Subject: RE: Filtering Oddity At 11:41 2019-05-15, Richard Kaye <[email protected]> wrote: >Gene and Woody's point is that XBASE tools are quite useful for us when >developing/testing, not that they are necessarily preferable for >production code. Exactly. One advantage that is particularly nice is that they are often short, simple, and fast. When I am chasing a bug or working on an idea, I prefer being able to get done what I want done fast. The protections that one might well want for an app are often not relevant. [snip] Sincerely, Gene Wirchenko [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/bn6pr10mb1458038f0ef0afc4880d6551d2...@bn6pr10mb1458.namprd10.prod.outlook.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.
