>If I delete a form (as opposed to 'remove'), it appears to leave the compiled version i.e. .FXP and a .BAK file. I must have spent an hour on friday pulling my hair out because a program that I had compiled always seemed to run using an older version and it turned out to be these FXP files that were causing the problem.
>
>Is this just one of those things I have to look out for??
>
>Also, having read up on these .BAK files I can only find them with reference to programs and tables. Does anyone know at what time these are created for forms (when you save, when you quit, when you compile...when?) and how to control them?
>
>And finally, with programs I've noticed there is this really useful (and obscure) setting that allows you to compile after each save. Can this cause problems and do I have to set it for each program??
>
>Thanks in advance
>
>Pablo

Pablo,
Forms doesn't compile to fxp files. Forms' compiled code is within the form (.scx) file itself as objcode.
Ones that compile to an fxp (prg, spr to spx, mpr to mpx ...) sometimes might be used from 'in memory' versions. Generally supplying .prg extension help but not all the time. Erasing a .prg and calling with extension immediately looks for and runs the .fxp version. This sometimes catches you but very rarely. 'Clear Program' might help most of the time. Erasing the fxp is the best solution IMHO.
It caught be once or twice a year and what I do is whenever I suspect of it I simply place a code something like a 'wait window' and if I don't get it, erase the .fxp and issues a clear program.
PS: Fxp itself might be last compile done forcefully with compile but still in memory code might be executing.
IOW I never learned the real cause and trained myself to live with it:)