I think the main point is that you can change the behavior (properties and methods) of subclasses but you can't change the behavior of VFP base classes. If you use subclasses exclusively then you will have the opportunity at some point in the future to change the definition of those classes and every instance where they have been used will adopt the new behavior upon recompilation. In order to accomplish the same thing with base classes you would have to change the behavior of each instance of their use.
I hope this made sense.

>Hi --
>
>My question is regarding sub-classing. I am approaching a point in my application where I need to tackle this, but since it is my first time, it is a little "fuzzy".
>
>My understanding of sub-classes is that I can create an object which I can use over and over again. For instance, if I have a command button (which is a base clase I believe), I can "sub-class a command button that says > "Open Form X" or whatever I want the button to say. So, I am inserting the sub-class object I created into my application, not specifically the base class.
>
>Is this correct?
>
>Could I build an application and just use the base classes? Or, would I be better served creating sub-classes for every object I want to create?
>
>*** Just trying to learn!
>
>
>Jason