Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Debugger/Path Problem

Status
Not open for further replies.

NullOp

Programmer
Jan 2, 2004
81
US
Using VFP 9 SP1, when I open the debugger and try to load a prog into the trace window from a subdirectory I get ye olde "Source is not available." I have dilligently set the path using "set path to..." and still, the same results. I've tried using the FoxPro and Debugger frames, no change. When I view the path I am seeing the expected results. Suggestions?

"Life Is Good!
 
What that error is telling you is that the date/time stamp on the .prg file is newer than the the .fxp file. The solution is to recompile, then open the debugger.

Craig Berntson
MCSD, Visual FoxPro MVP, Author, CrysDev: A Developer's Guide to Integrating Crystal Reports"
 
The date on the prg is 5/14/06, fxp is 10/27/06.

I guess my real question is why do I need to recompile an app that was shipped with freshly compiled progs.

In any case, recompiling worked, of course.

Thanks for the reply.

"Life Is Good!
 
>>I guess my real question is why do I need to recompile an app that was shipped with freshly compiled progs.

VFP executes the FXP but the source is stored in the PRG. If, for some reason, the date time stamp on the PRG is later than that on the FXP the source is, by definition, "out of date" and you get the error.

Perhaps the machine on which the PRG was recompiled was different than the one on which the PRG was last modified and the clocks weren't synchronized....


----
Andy Kramek
Visual FoxPro MVP
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top