>>That's a clear indication that something actually has the file opened for reading; if it were just an internal issue within the VFP session, Explorer would just ignore it and let you blast it out of existance.
>
>And I'm confident that VFP is the offender, at least from what FileMon tells me. And, no, none of your seven possibilities apply (well, maybe #7). Man, if someone could ever track this down, I'd file the bug in a heartbeat.

Mike,

Don't forget, it happens in FPW also. Seems to be related to encountering an error when the Trace is open. I'm wondering what sort of copy of the program the Trace window uses?