>Hello Hilmar,
>
>I'm sure you are aware that this is not always true...I run ad-hoc queries and forget to use NOFILTER all the time, and I usually have no problems running queries against the results.
>
>But for production code, NOFILTER is certainly the safer route.
>
>> NOFILTER is required if the result of a query is used for further queries.
Yes, sometimes it works, sometimes it doesn't. I got into the habit of
always (when I remember <g>) using NOFILTER for the first query in a series. It often happened that a report which used to work suddenly didn't.
It seems VFP decides when it is convenient to add the NOFILTER (implicitly), and the rules can change not only from one version to the next, but apparently also between different datasets. Perhaps the number of records, who knows.
So yes, my statement was not entirely accurate.
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
