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

This is why you have the path to your classes in the VFP Search path during development. This is also why you do not hard code the path in commands like SET CLASSLIB TO C:\Ker\MyClass. Instead you use SET CLASSLIB TO MyClass. When in development mode, VFP will be able to find the class because its location is in the VFP Search path. It works under runtime because it is included in the project. A class compiled in the APP does not need an embedded path.