Hi

Thanks Dragan. I was thinking I might be able to replace the classloc with just the file name. I still do some development on site but most of it is done in my office so your suggestion will help.

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?
>
>Keep all your class libraries in one directory, i.e. move them there, and

replace all classloc with justfname(classloc)

for each one of them. Then in your app you just include that directory in your path.
>
>That is, if you still have to do development on location. I was doing a lot of that some 8-12 years ago, and was gradually getting happier and happier as I pulled my self out of it. It's great at times, sometimes you even feel like the software hero who saved the day (ok, night - usually involved staying up late with them), but the code you write there is not your best, and nothing to be proud of. Last time I did it, it was like hell revisited, I've done a few great things, users were happy, and I thought I wrote some good code. Man, was I wrong. Took me nearly as much time later to untangle things.