Mike,

This is a bug in VFP. It occurs when you trigger the debugger inside a program that is not in the current directory. VFP will hold an internal lock on the fxp which prevents it from being rewritten. QUIT is the only way out.

The best thing to do is temporarily move the PRG to the current directory while you are debugging it, once it is debugged then you can move it back to the folder where you really want it.

>I'm debugging "error.prg", an error routine, quite basic code, except of course that I have to crash a "real" line to activate the error routine with the error I want to trap!
>
>Problem is, after examining the environment with the debugger & making a change, I can't recompile!
>( various messages about not being able to access "error.fxp" )
>
>I've SET PROCEDURE TO
> ON ERROR
> RELEASE ALL
> CANCEL
>
>and a few other things, but I can only recomplie if I QUIT vfp!
>( v6 with sp4 )