>In case you were wondering, the reason for all of this is that I use a poor man's source control....every time I release a build, I make a complete copy of all of the sources for archival purposes...but this doesn't make sense unless you can rebuild directly from what you saved. Needless to say, all of the paths VFP loves to store in ??x files makes for sticky resolution problems if future projects sources reside in different folders.

If your archive directories and development directories have the same structure, it shouldn't matter. e.g.,

** Development
C:\DevSource
       \_ Common
             \_ Libs
       \_ Project1
             \_ Libs
             \_ Progs
       \_ Project2

** Archive
F:\ArchSource
       \_ Common
             \_ Libs
       \_ Project1
             \_ Libs
             \_ Progs
       \_ Project2

if a class in the Libs directory inherit from a class in the Common directory, the path is ..\..\common\libs\superlib.vcx whichever directory they are in.
I admit that having to stick with a directory structure for all areas can be limiting, but I have found that it makes development a whole lot easier because I have a lot less to remember because it's always the same.