Right. Inheritance (which is what you get with VFP subclassing) is pretty much frowned on. There are exceptions, of course. Interfaces, Composition, Aggregation are much better OO practices.

>In C#/Java type languages classes are much more light-weight - your vfp instincts to keep it down to a low couple of thousand objects at most can be raised quite a bit. Every time you think about subclassing in "non-vfp" consider if it is not better to add an object to the class in question: much easier to add common behaviour to groups of controls, less typing. You might still subclass, but in the subclass not implement the methods in detail, but just use those of the added object. On the matter of typing: You will type more boilerplate code, from type declarations to interfaces needing to be implemented. There are compiler tricks to eliminate much of that - keep looking for a style that fits your mode of thinking.