>>>Why not just reference them as (HOME(1)+"\FFC\TheClassLib.VCX")?
>>
>>That's fine in code, but in the Project File, the path is hard-coded.
>
>Just copy the ffc to a path relative to your project - which will be stored as a relative path, instead of an absolute path that you may have had (or an off-the-root path, if on the same disk as the project).
>
>Actually it isn't hard-coded now, and never was. It's in the name memo of the pjx file. So it's not a literal in any inaccessible piece of code, it's a datum in a table, which was in your hands for the last 19 years (or whenever the first pjx file came to be).

My point was simply that the code technique mentioned would not affect the way the Project attempts to find the resource.

In my case, my app SCX, VCX, etc files are on a D:\XXX path and the VFP install path was C:\

And this causes the problem originally stated with working on a project file from both a Win 7 64-bit and using VFP installed in the default manner, and an XP machine.

There are indeed several ways to work around the issue.