>Rixon,
>
>The debugger can hold inappropriate locks on the fxp file if the file is not in the current directory. The easiest thing to do is to move the .prg to the current directory while you are debugging it.
>
>>I'm still having an occasional problem compiling programs. I have to quit VFP then come back in.
>>
>>I try the following before quitting VFP.
>>I run my CLEAR.PRG that has these lines of code:
>>
>>CLOSE ALL
>>CLEAR ALL
>>RELEASE ALL
>>CLEAR PROGRAM
>>
>>However, I get a source code is out of date error message when I try running the problem program. If I try to compile that program, I get a Cannot Create File error message.
>>
>>This usually occurs after I open a VFP debug session by setting step on. I close the debug session, then open the file and change it, then run the program and boom, I get the source code out of date message. I run the above CLEAR.PRG and I still get that message. I quit and come back in vfp and everything is fine.
>>
>>Any ideas?

If you are using a classlib in your app, none of the above will clear it from memory (other than restarting). If you use "SET CLASSLIB TO ..." in your code, you would need to add "CLEAR CLASSLIB ..." to your clear.prg.