Hi Renoir,

>I fight with this every now and again. Working on a project with additional >applications in subdirectories. Logic is to build a modified project, copy >the app to the main project directory and then build the main project. >Works great except when trying to debug. It never sees any code if it is >running inside any of the secondary apps. The path contains all the >directories under the main and if I put a step on just prior to the call to >the app it shows the pathing just fine. As soon as the call to the app is >done the source becomes unavailable. If I check the pathing at this point >it looks fine. If I issue a modi comm on an actual program along the path >it finds it and opens it. The only way I have gotten it to work is to copy >all the files from the secondary app directories into the main project >directory, delete the subdirectories and rebuild the main project. >Obviously this causes problems as after dubugging I then need to recreate >everthing to get it back the way it was designed to be so it can be checked >into VSS. Why can't the dubugger see this code if the paths are there? >Thanks!

I **DO** know the problem <g>...
your approach will work in FPW, but in VFP it will fail.
As faras I have explained the behaviour tomyself is,
that FPW's debugger works relative to the .pjx, whereas
VFP works relative to the targeted .app/.exe.
We used to buildto one directory "upstairs" and debugging
was still possible.

I also work with several subdirs for different parts of the app,
but I switched the location of the .pjx to the directory the app wil live later in. It is a PITA if you have dozens of small app's: so I rebuild them
into larger chunks, keeping the sources in different directories.

HTH

thomas