The thing I take away from all of that mumbo-jumbo technobabble is always add NOFILTER or READWRITE. When do you ever want SQL to give you a SET FILTER? If I want a SET FILTER, I write a SET FILTER. :)
>I'm having trouble understanding what the purpose is for NOFILTER. I often do not specify NOFILTER and then I use the cursor in a subsequent SQL statement without any apparent problem.
>
>Also, I've heard the following statement:
>
>"I believe VFP 5 doesn't have the NOFILTER clause; therefore I included an extra field in the following SQL,
which should produce the same effect."
>
>
>SELECT CustNo, Sales, .T. as DummyField FROM Table1;
> UNION ALL SELECT CustNo, Sales, .T. as DummyField FROM Table2;
> INTO CURSOR Temp
>SELECT CustNo, sum(Sales) as Sales;
> FROM Temp INTO CURSOR TempSummary
>
>
>How does this take the place of NOFILTER?
>
>Thanks,
>
>Yossi