>Without having seen the prior SELECT statements or the structures of the tables involved it is hard to answer your question. If you are getting a filtered view of the original table and would prefer a new temporary table either include the NOFILTER keyword in your SELECT statement
>as in:
>
>SELECT * FROM sometable INTO CURSOR somecursor NOFILTER
>
>or create a new field in the cursor as in:
>
>SELECT .t. AS whatever,* FROM sometable INTO CURSOR somecursor
>
>Good Luck

You can also do a WHERE .T. to force a file instead of a "filtered view".




>
>>Hi Dore,
>>
>>We just experienced for the first time that running a SELECT INTO CURSOR did not create a new temporary file, but a filtered version of the original table. This does however only happend with a specific table.
>>
>>Do you know why this is happending? Have we set some property without knowing it??
>>
>>
>>Thanks...
>>
>>Klas Nygren
>>
>>
>>>A stab in the dark. Is your cursor, cDl_dfltl, merely filtered versions of the underlying DBF, Deal , created with an SQL SELECT command? If so, the actual DBF is in use in the cursor work area, not a separate temporary table. You can easily tell by checking DBF('cDl_dfltl'). If it returns a full path to Deal.DBF instead of a temporary table, you will know that you are using a filtered version of the underlying DBF. If so, just add the NOFILTER keyword to your SQL SELECT statement to insure that a new temporary table is used for the cursor.