>Hi Al:
>
>If you are talking about "PRG" then 3 things came to my mind to check in this situations:
>
>1) DELETE all FXPs. Only rebuidling not always fix the problem, and sometimes some FXPs are not regenerated or not properly regenerated
>2) Make sure there is no change of directory in the middle of the system. Changing it makes VFP unable to find the original files.
>3) Make sure there is no redefinition a the library or function inside another EXE or APP, because sometimes this cause that VFP can't find the source too.

Yes to all of this, plus a clarification on (1). The recompile option is there for the build process, in project manager, and it will create new p-code for everything that goes into a project - which means database internal code, code inside reports, code inside vcx/scx, and compiled versions of prg code. The latter does not mean fxp files on disk. You can delete all the fxps you have, buld a project using rebuild option, and still have no fxp files. But inside the .app, .dll or .exe the latest version will be compiled. IOW, recompile puts freshly compiled versions of everything into what it builds, doesn't touch your disk.

update: just ran a rebuld/recompile on my current project. It recompiled all the vcx/scx/dbc, but didn't create any new fxp files - the latest is still two weeks old.

So, Al, to have your code visible in exe run in VFP IDE, you need the prgs with the same times as the build time and you don't need the fxps because they're inside the exe. The debug info is basically the filename (with relative path) and the line numbers. You can see this if you cheat - give it a prg with extra lines or simply paste the code from something else and then fake the file time, and then watch what you'll see in the debugger.