SELECT SQL for plain fields from a table results in a filter of the table rather then in a new cursor. subsequent CHANGES will alter the base table.
For your example try ?DBF() for both result sets.
Lutz
>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
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord
Weeks of programming can save you hours of planning.
OffThere is no place like [::1]