>>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.
>
>The one true and tried (and I learn it the hard way, having to resolve pathing issues after mistakes) way is to have _everything_ in a project in relative paths. If it means that there may be some common stuff among the projects, which may be in ..\libs or ..\framework\bitmaps, so be it, but literally everything should be in the same directory tree. Which also meant that none of this tree should be below home() - different machines may have Fox installed at different places, and the project shouldn't care about that.
>
>(my point was about word inflation - "hard coded" means "buried in code as a literal", not "stored in metadata" and not "absolute path")


Point taken on all accounts. Especially the relative paths thing. Since I haven't changed dev machines in about 5 years, my previous setup has worked for so long that I never had to deal with anything in my paths, even though parts of my app are (*WERE*) under different roots.