>>Using IIS 4, after a file has been recently accessed by a browser, if I try to ERASE that file, I can't. I have to wait a few minutes before I can erase the file. After the file is sent to the browser, that file should not be locked. How can we avoid that?
>
>I imagine you would need to stop/start IIS, which probably is not acceptable on any busy site.

I don't have to. After a few minutes, I can get access to the file again.

>For problems like this (temporary PDF or HTM files), I queue files to be deleted into a DBF and a VFP maintanance routine will erase them on a schedule. It will try again later if the file could not be opened.

In my case, this is a robot which need to update some files on the server. The update must work all the time.