>>>>Is there some way of getting VFP to update the source. I have a .prg that shows "Source is out of date" in the debugger. The file has been recompiled. The .fxp file is up to date. There are no other copies of the file on disk. I've even exited VFP. But it insists on running the old code. This is happening much more frequently than it used to. (VFP 8 SP1 on XP Pro). I'm even beginning to suspect the OS!
>>>
>>>Are you sure it's showing this error for itself? Or is from something this program is calling? i get that every now and then
>>>
>>>at any rate, erase the fxp file and run the prg.
>>>
>>>i've got to where i erase all fxp's in my working directory tree periodically out of a habit i picked up using vfp3 beta :)
>>
>>I have erased the fxp. That's what's frustrating. I'm running the prg directly (well trying to anyway). I suspect it's a problem in that the same procedure is in a compiled .app file and VFP rememebers that internally so when I say
>>do qcrypt.prg
>>it'll find the one previously compiled into another .app file which may have been run earlier rather than from the .fxp on disk.
>
>Very good hunch. Have you tried CLEAR PROGRAM before DO QCRYPT.PRG? Is the prg found earlier than the proc in the app? If that app is a procedure file, then it's probably found earlier than the prg. Anyway, my advise is to prevent any name clashing.

It was an app. It wasn't a name clash, the same .prg is used in a .app (which was older).
What I really need when these things happen is for the debugger at least to identify the source, even if it is out of date. Would save a lot of time somedays.