I have a corrupted file on the Windows NT 3.51 server.

From Visual FoxPro, if I do ERASE (lcFile), from a workstation, I will have the Visual FoxPro error message File access denied. If I run it from the server, I will have the server message saying the File is corrupted and that I need to run the checkdsk utility to fix it. Since, from the NT the error message is fired from the OS instead of Visual FoxPro, this is locking my application because it does not go into my error handler.

What kind of mecanism can I use from Visual FoxPro to avoid having the OS error message and deal with that from Visual FoxPro?

Basically, I just want Visual FoxPro to not try to erase that file if it is corrupted. I know that I will have to reboot the server to fix the file but I would like Visual FoxPro to detect it so it won't lock the application so I can reboot the server at a later time and have the application continue as usual.