>>If your archive directories and development directories have the same structure, it shouldn't matter.
>
>Yeah, I kinda thought something sensible like this might work. I guess the rule is VFP will store a relative path if it can, and a fixed path otherwise??

Basically, yes.
VFP will (i.e. should) only store a fixed path if the class inherits from a class on a shared network drive; or if it can't find the class library as indicated in the current relative path - which may be the case if the directory structures are different.