> You're right. The PM stores the path to files. Actually, it stores the path relative to the project's home path. This lets you reference common class libraries, procedure files, screens, etc from a folder that was not necessarily in your path.
>Rather than try to trick the PM into finding your file, you could:
> 1. Copy the file to the local drive
> 2. Remove the file from the Project Manager
> 3. Add the local file to the PM
> Now the PM knows which file you want. Reverse the process when you are finished with the file. By the way, be careful to remove the file from the project and not delete it fom the drive. (That's why I suggest copying the file first, to protect you from a slip of the mouse.)
> If you have time, this is the perfect application for a project hook. You could flag a file as "Editing" and when you open it, the code in the project hook would know to open the one on your local drive. I have never done it, but it ought to work.

Yeah. I know about copy,remove,add ... it's kind of a pain in the neck but that's been my methodology so far.

You talk about a "Project's Home Path". Not sure what that is or how to read/write it.

Do you know how to inspect the path associated with a file that's in the PM? That would be really useful.