>>What can be the reasons why the Visual FoxPro 5 Erase command will generate a File Access Denied? I have a process which is using the Erase command to remove some files. That process is executed several times per day. However, a few times per week, I have a log which says File Access Denied.
>
>Apart from the usual reasons, you don't have permission, the file is read only etc.
>
>If it happens on a temporary file its likely that whatever network or OS has the file open 'believes' that a different process has the file already open. If you are absolutely sure that you are always closing the files before opening them check with the Network OS that there isn't some buffering problem. If its that you are creating temporaries, closing then deleting them try delaying deleting the files after closing them for as long as possible.
>
>You might also make sure that you haven't got a different data session running.
>
>Simon

Hi Michel,

The "different datasession" is the one that foils me usually. I'll create a cursor in one private datasession, copy it to an independent dbf, open up another form which has it's own private datasession and find that neither form will be able to erase the file I created. I think that both data sessions seem to think that it is somehow connected to it so ERASE fails.

I haven't gotten around this one yet.

Steve