Jason,

You seem to be on the right track here. Just to clarify, in your application you would create objects that are "instances" of your sub-classes. You can use the base classes in your application, but it's definitely a good idea to create a sub-class for every base-class you're going to use. This way you'll be able to make wholesale changes to your application when necessary just by changing your classes.

It's a good idea to create a generic "one-off" subclass for each VFP base class that you'll use. You can then sub-class your sub-classes to create more specific classes like a Cancel or Save button.

>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