Hi,

First of all, thanks for the replies and advice you guys sent.

I think I found out why. It seems that when the select does
creates a temp file when the order by is an index set to unique.
I tried it with a regular index as order by and it just created
a cursor based on the table (more like a use again) which is
what we wanted in the first place.

Thanks again


>>>Hi,
>>>
>>>Hope someone can help me with this. We have an application
>>>that creates cursors in the MAIN for use in the whole app.
>>>Problem is some of the cursors seem to be copies of the
>>>actual table (has all fields and indexes) and exist as actual
>>>tables (CSAMPLE.DBF) while others exist as cursors (stored in
>>>the temp i.e. C:\TEMP\01021598.TMP) when we do display status.
>>>
>>>The syntax we use is the same for all using sql select. For
>>>example:
>>>
>>>select Field1, Field2 from Sample order by Field1 ;
>>>into cursor cSample
>>>
>>>select Field1, Field2 from Sample2 order by Field1 ;
>>>into cursor cSample2
>>>
>>>etc...
>>>
>>>TIA
>>>
>>Hi Arriyel,
>>
>>If I recall correctly, the location of the tmp files generated by an SQL statement is determined by the setting in the CONFIG file. I think it's SORTWORK.
>
>If SORTWORK isn't specified, it uses the TMPFILES entry if that's present. If neither is specified, I believe it defaults to the startup directory, which can be disasterous if you start on a CD or in a directory where you don't have write privileges!