There may be something in the program that is keeping it in memory. before you make any changes you might try

RELEASE ALL
CLEAR PROGRAM

To make sure the fxp is not in memory. The auto recompile may not be working (can't write the file) but it may also not be returning an error. Just ignores.


>Dear Andrew,
>
>Thanks, but No Help! Something other than Set Development on is the culprit. I haven't gotten mad enought yet to give it
>a real test using really simple bare bones prgs, but I'm getting close.
>
>Here is what I have found so far. Remember That BOB.PRG calls JACK.PRG. When using the DEBUGGER and
>canceling to make mods to JACK.PRG, JACK.FXP is being locked out, frozen, or otherwise made not available to
>be overwritten. BOB.PRG,if modifed is not affected in the same way.
>
>After modifying JACK and re-running BOB, the "Source Out of Date" messages comes up in the trace window and
> the debugger runs the old JACK.FXP. If I cancel and try to ERASE JACK.FXP from the command window or
> try toCOMPILE it from the PROGRAM menu, I get a "File in Use" error message. If I try to DELETE it from the
> W98 Explorer, I get an "'Access Denied" error message.
>
>The Only way is to exit VFP and start over.
>
>BTW the Help file says that SET DEVELOPMENT ON is on necessary if we are using an external TEXT EDITOR
>to modify our prgs. When using the VFP text editor, we are supposed to get an automatic compile when we
>run the program after modification regardless of the setting of DEVELOPMENT.
>
>Any other ideas.
>
>I will continue to play with this thing and run some specific tests, carefully documenting what happens when.
>I will try a third prg being called by JACK to see if their is any wierd stuff there also.
>You will get my results in a week or so. Other things are higher priority right now..
>
>Thanks again for your time and suggestions
>
>F.Bennett Swenson