>>If you do a SELECT * FROM sometable INTO CURSOR xyz, I've never seen it do ANYTHING but a filtered result set. Only if you add some kind of other field, join another table, not match an index key, WHERE .t., NOFILTER, have I seen otherwise. I would not have a problem with a SET SQLFILTER ON/OFF or some other kind of setting to control it, but I need the "filtered view" as it currently exists.
>>
>
>Christof asked for an example and, unfortunately, I cannot supply one. I have been using NOFILTER since it became available, so maybe that explains something.
>But as I say, others here have reported it. Hopefully they may chime in with examples.
>By the way, I wonder how you can be **certain** that you always get a filtered result set??? Since your programs would be coded in such a way as to function correctly with a filtered result set, and since a cursor would let the same code function correctly too, How can you be so certain???

Hi Jim -- I can guarentee you that Christof is not correct on this, at least not in vfp5 or 6. I just a week or so ago tested this for another thread (with Walter Meester). The simple SQL result INTO CURSOR without NOFILTER is totally unpredictable. I tried many times to get a filtered table in the Command Window, with no success. Then all of sudden a little later, when I didn't want one (still doing some work in the Command Window), by Murphy's Law (or something :), I got one.

Vfp apparently has its own mysterious way of deciding when to create a filtered result set, probably based on factors like file size, available memory, and so forth. As