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 <profoxtech-bounces(a)leafe.com> On Behalf Of Gene Wirchenko
Sent: Wednesday, May 15, 2019 2:55 PM
To: profoxtech(a)leafe.com
Subject: RE: Filtering Oddity
At 11:41 2019-05-15, Richard Kaye <rkaye(a)invaluable.com> 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]