This is what I see when I open the debugger' Trace window. Right before I begin any execution but after the form with all the controls and all associated prg files is brought up.
I want to know what source it is talking about. Is it source code In which sense is it out of date Is it my source code or FoxPro's in some way I may believe that I perhaps use some operators that have been deprecated but there is no indication where to look.
I do not use the trace option. As the worst case scenario I would use breakpoints so I do not have much observation as to how it changes if at all during debugging but it seems the message stays put.
How can I get at least some answers to these questions
The whole thing is of somewhat abstract value for me. This message does not stand on the way of my debugging. I just want to know if it is perhaps a symptom of a greater problem.
Thanks

Source is out of date
Ludy
New thoughts! Thanks you.
I did get the latest DVD with FoxPro9 a month or so ago but did not bother installing it since there were no signs that it was anything but just VFP9+SP1 and I do have SP1 installed superimposed on the VFP9 installed back in August of 2005 I believe.
Do you have that DVD in mind when you are talking about the latest version or you mean something downloadable from MSDN websites
If you could be more specific for an ignoramus that will be greatly appreciated.
Thanks.
HIRU
Thank you very much.
I hope it is just a notification. It should not change the execution in any way, right
ZeBobo5
jettman
I mean the latest ver of your prg file.... when compiled it creates the FXP, if your fxp has a later time stamp than the prg the fxp may not have all the changes you made in your prg.
Dave
Jerome Le Bateau
It means you may not be running the newest ver!
That would change the execution.
PlasticLizard
arndawg
Tim T
If you could be more specific for an ignoramus that will be greatly appreciated.
From the VFP on-Line help:
Source code out of date
The date source code you specified does not match the compiled (.FXP) file.
The solution is to delete the .fxp file so that it will be recompiled the next time you run the .prg.