>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.
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.
-- Randy
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only