Richard, instead of grabbing all of your Data from the server and consequently filter to the data you require you could also consider to select just the subset of data you require in one go. That seems faster to me. Also how do you 'grab' the data from the server. Also I dont see why creating a subset of your equired data from your data is better than to set a filter. Anyhow this still seems to me a matter of taste, a matter of coding, as no one can ever see the difference in the endresult between a set of data with select..where or set filter to.. it is your preference and in case you are fine with it and you dont intend to do this in a enduser environment I would just do it the way you think is best for you.
Regards, Koen Op do 16 mei 2019 om 22:36 schreef MB Software Solutions, LLC < [email protected]>: > Hi Koen, > > I respectfully disagree. In my case, I grabbed all of the Server data > locally into a cursor, and then I use the SET FILTER on that to show the > respective data when appropriate. This is better than repeat trips to > the Server via the SQL SELECT. I'll take that bet every day of the week > that ends in 'y' . ;-) > > > On 5/16/2019 1:26 AM, Koen Piller wrote: > > Richard, > > what you describe is a matter of personal taste. > > There is no overhaed in building a cursor with select * from myData where > > unpaid<>0 into cursor curUnpaid vs set fillter to unpaid <> 0 in myData. > > I, personaly, would prefer #1 in the enduser environment environment# 2 > in > > my development environment - version(2)#0 vs version(2)=0. > > There is also no need to call a select() statement an overhead. > > Regards, > > Koen > > > > > > > > Op do 16 mei 2019 om 00:23 schreef Richard Kaye <[email protected]>: > > > >> 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/CACUu1SvotHDXjQyOznNcUK8=7r9oas6iudbj6pbka8el+so...@mail.gmail.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.
