>>>Now here is more strangeness. I mentioned that I had setup a duplicate SQL cursor called curTest which also failed before. Well when I add NOFILTER to the real curROWNER select statement then NEITHER cursor fails. That is both cursors retain their records even though only one has the NOFILTER clause.
>>>
>>>Peter Robinson
>>
>>Without NOFILTER you trust VFP to decide (and it may decide differently every time) how the cursor will be created: as physical file or as filter on real table. With NOFILTER you make sure that it's physical file.
>
>And vfp's decisions are such that an SQL will work fine without NOFILTER hundreds of times on different machines over months, and then all of sudden, Big Problem With Filtered Table in app...so NOFILTER is now essential, really, for most situations...

and it brings back DELETED() issue :-), i.e. interface tuning becomes more important.