That is correct, in the early days when OOP was introduced to VFP, subclassing was the holy grail of everything.
Since I am working in .NET (besides of VFP) I moved more away from inheritance and try to solve this with composition whereever possible and reasonable, also in my VFP applications.

>It comes from your FoxPro background, where the norm was "subclass everything". I've *never* seen that pushed in .NET, even with WinForms.
>
>>Ok, now I understand. I was having trouble comprehending this morning what it was that meant. I agree, on both counts. I have been doing MVVM as well and right now dealing with an application that has every control subclassed and because of this, no designer support on any visual view. Everytime something is broken we have to first determine if this is because of the subclassed controls. Even all the third party stuff has been subclassed. I am not thinking this was a great idea.
>>
>>Thanks for clarifying.
>>Timothy