>>No. The PRG time stamp was older than the EXE, and the FXP was older than the PRG.
>>
>>I manually recompiled the PRG so the FXP datetime is current, then rebuilt the EXE.
>>
>>Problem persists - works on my machine, doesn't on another.
>
>The source in the vcxes is inside the exes, for prgs, however, only the fxp is in there. It works on your machine because the physical prg file is still on the disk - try to do this with prg renamed (or its folder renamed) and you shouldn't see the source in the debugger on your machine either.
>
>If you want to see it on the other machine, bring the source over, on the same relative path to where exe is run.

With a basic test, you're right. In my source tree, I temporarily renamed the source for the procedure file and when debugging got "Source not available". That's interesting, I would have thought that enabling "Debug info" in the Project properties would automatically pull that in, but obviously not.

When I copy my source tree to the remote site, now I get the dreaded "Source is out of date" message instead. What I've tried:

- Rebuilt the app with the compile all files option enabled
- Created the same directory structure on the remote machine and copied my entire source tree there
- Transferred files in a zip rather than directly using Dropbox. With the latter the files on the remote machine get the datetime of the download which can cause problems
- Tried running VFP (within which the EXE is run for debugging) as an administrator
- Tried running VFP in Windows 7 compatibility mode (on the Windows 10 Pro remote machine)

Hmm, just noticed something. In the same folder as the PRG there was an FXP with a slightly older datetime. This is even after rebuilding with the "recompile all files" option.

I deleted that FXP and rebuilt again with recompile all. The EXE is built but there is no FXP file in the same folder as the PRG. Makes me wonder just exactly what's happening with recompile all.

Both before and after this operation the EXE in debug mode was working as expected on my machine. I'll find out Monday whether it makes any difference at the remote site.