Hi

Thanks Dave I downloaded a copy. It certainly looks easier than going into the files manual which I often do.

Simon


>>Hi
>>
>>In the past most of my standard code was stored in prg files in my software library. When I wanted to deploy an application on a customer's computer I could simply drop the files into a subfolder beneath the application root and set the path appropriately and everything worked fine.
>>
>>However, I now use vcx files and they have relative paths stored in the table specifying where to find the parent class. If I place these files on client machine VFP reports that it cannot find the parent classes even if the class library is loaded using SET CLASSLIB TO. I sometimes have to do development work on the client machine and I am not always able to match the folders on the client machine with my development machine so I am always running into problems with these path names stored in the VCX files.
>>
>>Does anyone have suggestions of how to avoid this problem?
>>
>>Thanks
>>Simon
>
>check out an application called "HackVCX" by Rick Schummer
>
>http://www.askam.com/rschummer/vfptools.htm
>
>I highly recommend building the class libraries right into your project.
>So the EXE file is built and finished and not 'open ended'.
>
>hope this helps