>>>>A class library is not searched unless included in the library search with SET CLASSLIB at runtime. Putting it in the project, or in the directory with the app, won't access it automatically - untiladded to the SET CLASSLIB list, VFP ignores it.<<<<

Ed,if I follow what you are saying, does'nt this defeat the whole purpose of Inheritance ?

I have all my classes set up in one particular Folder, Say C:\KER
Now ,all my individual applications which refernce these classes will be in different directoies. Up to now, I could easily include these as part of my project. But with the Set Classlib command, am I right in saying that I will have to either:
(1) Issuse a Set Classlib to C:\Ker\Myclass and ensure this is on the clients machine
or
(2) Copy all my classes to my specific application directory

This does'nt sound right so maybe I've missed something ?

Regards,
Gerard






>>Mark,
>>Even though the Class is part of the project (I checked this) why do I still need to put it in a Path just for this command ?
>>
>
>A class library is not searched unless included in the library search with SET CLASSLIB at runtime. Putting it in the project, or in the directory with the app, won't access it automatically - untiladded to the SET CLASSLIB list, VFP ignores it.