So I've decided to port my class library to my partner's machine, and here's what happens: the paths to many things are hardcoded into the ..vcx, so when we run it on his machine, the bloody thing can't locate comctl32.ocx, because it doesn't look for it in "there where the Windows system directory is", but in "c:\w95\system". Of course, his Windows directory is "C:\Win95", and the .vcx knows nothing about it. There were some other glitches like this: I've installed VFP in c:\vfp, while he did it in d:\vfp, and there was also some problem with that. Could "Set Path To ...;c:\w95" have helped with this? I mean, if we include the Windows and Windows\system directories into the VFP path, would it stop writing full paths into the vcxes? Any other idea? I can't figure out how would it work in a compiled .exe, if it had the paths to the .ocxes hardcoded in the .vcxes, and then on install found that the .ocxes should go to some other directory (not the same as on the development machine). How'd it find them at runtime then?