Re: Filtering Oddity

On Sat, May 18, 2019 at 12:01 AM Fletcher Johnson FletcherSJohnson@yahoo.com wrote:

1. It used to be that a Select statement would be optimized by VFP to open

the source table again, in another work area, and then set a filter on it. This was a problem when people thought they had a cursor and updated the contents, only to find out they had edited the actual data. So they added a "nofilter" clause that forced VFP to create a new cursor and not use the original approach.

Had to be bad coding, possibly mixing up aliases in the process.

5. I can't remember, but did set filter allow you to reference a variable?

And, if so, did changing that variable then change the effect of the filter? If so, this might also be an option.

SET FILTER can use variables. Changing the values of the variables should not affect executed SET FILTER if I remember correctly.