>>>>>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 ?
>

No, it just means that the lights are not automatically turned on just because there's a light switch on the wall. You have to let VFP know when the class library is allowed to be used to provide classes, just like you use SET PROCEDURE TO to list the files that may be searched for functions and procedures. Just having a procedure file in the project will not allow VFP to use it automagically. Just issue the necessary SET CLASSLIB TO and it works.

>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
>

No, hoiw about issuing a SET PATH TO that includes C:\KER and issuing a SET CLASSLIB TO MyClass ADDITIVE to add it to the list of class libraries. You have to actually read the manuals at times.

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

Basic understanding of how VFP resolves paths and classes.