>>>>>>I'm having trouble with an SQL statement that creates a temp dbf. Its a standard statement Select * From...
>>>>>>Sometimes the created file ise set to exclusive use, and sometimes its not. This occurs even if I set exclusive off and then close and reopen the temp file. Any Clues?
>>>>>
>>>>>Normally all temporary files/tables created for exclusive usage, and logically it's right because this is strictly local file. If you close and reopen dbf file with command USE ... SHARED it must be open as shared. And in faxt it's not temporary file.
>>>>> May be your meant cursors? These are really temporary tables.
>>>>
>>>>Concur. This Temp file is actually a file which will be manipulated in network environment ie... adding/deleteing/indexing and then disposed of after reporting. Hence read only shared access is not desirable. Should we try using the SQL Create Table and then SQL Insert to build a sharable Temp Table.
>>>
>>>If you really need in temporary shared DBF you can use EITHER Select-SQL and then Use, Use..Shared OR Create Table and then INSERT-SQL. Also you can use COPY TO and probably many other XBASE commands.
>>
>>
>>you can also create cursor mycursor (textfield c(20), etc.) user who created can add, edit, delete, index, etc. however, no one else can...
>
>Do you know how to use Cursor in shared mode??

The real problem we are having is the inconsistentcy of "EXCLUSIVE ON|OFF". Sometimes the SQL Select results in a file which has EXCLUSIVE ON sometimes it results in a file with EXCLUSIVE OFF. This generates a random error indicating that we must have exclusive use of the file to accomplish desired results. Using SET EXCLUSIVE has no effect. Its almost like the EXCLUSIVE status is being embedded in the file header with no way to change it or predict its value.