>>>>And the product is called Visual Studio and everything is class based - what a joke.
>>>
>>>
>>>The fact that there isn't much visual inheritance in VS does not make it a joke. The visual is the preview that you have in all of your design efforts. I like the fact that everything is class-based.
>>
>>Well said. Besides, how often do we subclass GUI components (in any development environment)?
>
>Very often if you really follow OOP. In fact you never use a base class if you can help it. You inherit not cut and paste if you want to change/modify functionality.

Thank you for the tutorial but I didn't just fall off the turnip truck, Bernard. I am quite familiar with the principles of OOP. One of the things that might be said about it is that excessive use of inheritance is the sign of a neophyte. (Not directing that at those who posted yesterday in favor of inheriting base classes two levels, one for the company and one for projects within a company; I like that). Done improperly, you can quickly wind up with a maze of classes that aren't a lot more maintainable than "spaghetti code" in the old days.