Todd,

>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?>

There's really no problem doing this...it will certainly get around the problem!

This VFP bug still bites me once in a while (even in VFP6) but I haven't been able to pin down the sequence of events.