Hi Walter,

... And I would bet that if the VFP team eliminated them (ie made NOFILTER the internal default) then no one would even notice and there would be no problems from that release onward.

Cheers,

Jim N

>Jim,
>
>I agree that this feature is giving a whole lot of trouble. Though some will say it can be used to optimize your application, you can always set a filter: like:
>
>USE TABLE
>SET FILTER TO expr
>
>This filtered tables feature is absolutely of no added value and is the cause of a whole lot of trouble. I would recommend the fox team to switch the default behaviour from filtered to non-filtered resultsets.
>
>Note that the most of use use the SET DELETE ON settings in his/her applications. Since i'm against the use of a DELETED() tag I normally don't experience these resultsets (because fox can't fully optimize the query), but if it can I'll be banging my head against the wall why the program does not work as espected.
>
>Walter,