Bela,

Obviously you've created a fully optimized SQL query. VFP then decides rather than to create a readonly cursor, to set a filter to the original table. To avoid this situation, just add the NOFILTER clause to the SQL SELECT.

In this cases VFP alway creates a temporary cursor. And yes then it's save to use it again to make it writable, so it behaves just like an ordinary cursor.

Walter,

>
>I found the following syntax to make a cursor writeable:
>
>USE DBF("cMyCursor") IN 0 AGAIN ALIAS cAnotherCursor
>
>But if I use the following :
>
>select anyfield from MyTable into cursor cMyCursor
>
>then DBF() gives back the path of the original table, but I don't want to write into the original table.
>After some reasonong, I have tried using the following:
>
>select anyfield from MyTable into cursor cMyCursor nofilter
>
>then DBF() gives a really temporary filepath.
>
>According to the VFP documentation, neither of the previous syntax creates phisical files. But practically, the second syntax still produces one.
>
>Is it sure, that the second syntax always produces a temporary file, and thus, is safe to write into the cursor after making it writeable?
>
>P.S.: I know, that
>
>select anyfield, .t. from MyTable into cursor cMyCursor
>
>does the job, but I would like to understand the theoretical background.
>
>TIA
>
>bb