Yeah, I'm classifying it as a bug too.

Barbara

>Craig,
>
>the following is cut from VFP 5.0a HELP of SELECT- SQL... ------------
>Include NOFILTER to create a cursor that can be used in subsequent queries. In previous versions of Visual FoxPro, it was necessary to include an extra constant or expression as a filter to create a cursor that could be used in subsequent queries. For example, adding a logical true as a filter expression created a query that could be used in subsequent queries:
>
>SELECT *, .T. FROM customers INTO CURSOR myquery
>
>Including NOFILTER can reduce query performance because a temporary table is created on disk. The temporary table is deleted from disk when the cursor is closed.
>
>end of paste from VFP HELP
>
>As you can read for yourself, it says that a temporary table WILL be created. Now I would agree that it doesn't say that it would create a genuine (useable) DBF-NAME, but that would seem to be a logical assumption given that a table is created to disk (how else would one reference it?)
>
>SO. . . I would classify Barbara's experience as a bug, and certainly not a "design feature".
>
>Cheers,
>Jim N
>>>I have a cursor (VFP50a, Win95) which has a filename assigned, which can be read with dbf(). However, the file does NOT exist in the temp file. I've checked that the temp directory DOES exist, and that the cursor exists - I can browse it. However, I can't access it with the filename.
>>>
>>>There are work arounds, such as using a table and deleting it when the form closes, but I'd like to know why there's a file name but no file. I'm assuming the cursor is completely in memory, but don't know how to work with it.
>>>
>>>Dragan Nedeljkovic mentioned something similar in the 'View, cursor or something else?' thread a week ago. Anyone else have this problem? And found a solution?
>>>
>>>TIA
>>>Barbara
>>
>>
>>You do not have control over whether a cursor gets written to disk or not. If there is not enough physical memory to hold the cursor, the disk is used.
>>
>>Craig