>Hoi peter,
>
>
>>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??
>
>
>As you know I'm not a Microsoft representative, but I'll try to explain the cause of the behaviour:
>...
executing the module in the same directory of the project and it thus cannot find the contained objects. I suspect this behaviour is by design.

Hi Walter. My guess is that it's not 'by design' but that the VFP-team simply forgot to serve those who want to put each 'project' in a separate map.

>
>One workarround that should work is to move the project files to the same dir where the app is executed and tested, and build your application from there.

Well, it's exactly this situation that I want to prevent! I not only put each module/project in a separate map; I also arrange that - when building the app - no stuff is pulled in that's outside the map (with 'set path to'). Thus I get clean, small modules.

>In the past i've tried to hack those files and remove all relative pathing (with JUSTFNAME(), this way VFP does search trough the path setting), however, this causes problems when developping because the project manager might not find all objects again.
>
>I've played with the thoughts of building a project class which would make a copy of the project, remove all overhead from the sourcefiles and build from the copy. However, I never started this project and don't know if this even would be possible.

I'm sure it's possible. If no one else comes with a better solution we might try this idea together.

Bij de weg, ik heb nog steeds plannen om met z'n allen op de hei te gaan workshoppen. Misschien moeten we maar eens een datum gaan vaststellen?!