The application we build consists of several APPs, each of them in the same map as the EXE.

In the development environment we have a submap that has a submap for each APP's project file and its specific source code.

E.g.

	C:\WhatEver\WhatEver.EXE
	C:\WhatEver\Module1.APP
	C:\WhatEver\Module2.APP
	*
	C:\WhatEver\Source\WhatEverMain\WhatEver.PJX
	C:\WhatEver\Source\Module1\Module1.PJX
	C:\WhatEver\Source\Module2\Module2.PJX

When we want to build an APP, we switch to its map:

	e.g. to C:\WhatEver\Source\Module1

and then build the project file using the different destination map:

	e.g. BUILD APP C:\WhatEver\Module1 FROM C:\WhatEver\Source\Module1\Module1.PJX

So, the APP is built into another map and also we'll execute it in that other map.

We've noticed that this has consequences for the availability of debug-information (presumed that debug-info is included anyway). Debug-info seems fine for forms and classes. However, when debugging a PRG, the Trace-window has a message 'Source not available', even if the PRG is available along the searchpath.

In case a Microsoft representative reads this message: We regard this behavior to be a real vfp-quirck, because we can't imagine that it's 'a feature by design'. What's your vision??

Here's the question for All: Does anybody know of a workaround??

---------------------------------------------------------------------------
Peter de Valença - ViaFox - http://www.viafox.nl
Currently contracted by KLM - Royal Dutch Airlines
---------------------------------------------------------------------------