>>>I am completely stumped by this error (error 1815). The error is listed in the help as...
>>>
>>>*****
>>>"cursor" must be created with SELECT ... INTO TABLE (Error 1815)
>>>You have tried to use a repackaged cursor as a source for another SELECT statement.
>>>
>>>Some cursors cannot be used in successive queries.
>>>Use the INTO TABLE clause of the SELECT - SQL statement instead.
>>>*****
>
>>You should SELECT ... INTO CURSOR ... NOFILTER
>>BTW, it may generate error in VFP5 too
>
>Thanks Ed, it worked.
>
> I am still making the transition from VFP3 where I didn't need the NOFILTER clause. What I find weird is that I use successive queries throughout my application and they all are working (except the example given) in VFP6. Very strange... In the morning I will put NOFILTER in all those queries.
>
>Thanks for your help.

Evan- this problem arises out of the fact that VFP 'repackages' a table (applies a filter to it) when you only select fields from one table. This is soleley for performance reasons.

You can demonstrate this by running your original query above and then issuing

?DBF()

You will see that the original table is the underlying data.

Running the same query with NOFILTER, and then checking DBF() will return something like C:\temp\1355233.dbf

VFP is unable to do this repackaging when you join two or more tables, or when one or more of the fields in the result set are calculated. It is forced to bypass this feature by the NOFILTER clause.