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.

>time stamp on the PRG is probably newer than the time stamp on the exe.
>
>
>>I'm debugging an EXE run within the VFP dev environment. I'm stepping through some method code and the next step is supposed to go into a function in a .PRG procedure library.
>>
>>Everything appears as expected in the Trace window up to and including the method code.
>>
>>On one machine (my dev box) the step into the function call works fine, the code shows in the Trace window as expected.
>>
>>On another machine at a different site the exact same EXE shows the method code in the Trace window, but as soon as the function call is entered the Trace window shows "Source not available".
>>
>>I have confirmed that:
>>
>>- the procedure library is included in the project
>>- it appears to be OK - can be opened and viewed
>>- the EXE was built with the "Debug info" option checked/enabled in Project Info (and "Encrypted" unchecked/disabled)
>>
>>What might be causing "Source not available" on the second computer?