>I don't like the idea of getting bit by a prg not re-compiling into an fxp and an outdated fxp staying in place. I know this is a FoxPro issue, but what can we do in MM? Can I put the following lines in my startcb.prg to try to cut down on this problem? Thoughts? Ideas? I probably need to do this for screens also huh? I know this causes them to re-compile everytime after I run STARTCB.PRG, but I prefer that over getting bit by an outdated .fxp. Is there any reason why I would not want to do this?
>
>Following code into startcb.prg?
>
>delete file D:\CDBK30\COMMON30\libs\*.fxp
>delete file D:\CDBK30\COMMON30\progs\*.fxp
>delete file D:\CDBK30\COMMON30\utils\*.fxp
>
>(Where TRACKING is my specific projects directory)
>
>delete file D:\TRACKING\libs\*.fxp
>delete file D:\TRACKING\progs\*.fxp
>delete file D:\TRACKING\utils\*.fxp

Why don't you set development on if you are running foxpro if there is a fxp that needs to be recompiled it will do it when running the program.