Source Code out of Date?

[RPowers]

I am getting source code out of date when I compile my code and can not find newscr.prg messages with some projects that I am working on in DOS Foxpro 2.6. Anyone seen this before?

 

[virgo]

I haven't seen this exact error. However,....<br>
<br>
I do some work in FoxPro 2.6. And, things need to be compiled all together...<br>
<br>
My 'favorite' truck is to put together an index on the file for something that I want to do. This index along with the compiled material, all screens, prgs, etc. , can cause the 'source code out of date'....

 

[JasPerth]

I have found that sometimes foxpro thinks it has re-compiled a program when it has not. I have found that buy deleting all the compiled program files (i think they are .fxp, from memory) then re-compiling the source code I get around this error.<br>
<br>
eg original program runprog.prg<br>
foxpro compiled runprog.fxp delete all of these then try again.

 

[tonni]

In Foxpro for Dos, when you use external editor and you saved your modified program. But the Foxpro didn't know that program has modified, then when you build a application or executed file the foxpro only used .fxp file for the appliacation that you builded.<br>
You can do these :<br>
1. use foxpro internal editor and set development on<br>
2. use external editor then you recompile all the .prg file in foxpro.<br>
<br>
<br>
<p>TONNI<br><a href=mailto:uatnehc@bdg.centrin.net.id>uatnehc@bdg.centrin.net.id</a><br><a href=

http://sites.netscape/uatnehc/homepage>Fox

Forum</a><br>

 

[rgbean]

I've found that most of the time you get this error when the files in your project are spread over multiple directories. Then if you are debugging, it's critical to make sure that your current FoxPro PATH includes all those directories. Also, it's important that they are in the order you want to FP to look for the files. i.e. If you have multiple copies of a file, make sure the one you have in the project is first in the PATH setting.

The problem seems to be that while the project knows where to get the files from to create the code file, this information isn't stored in the .APP/.EXE, so the debugger must locate the source files based on the SET DEFAULT and SET PATH settings.

Rick