Actually, when you sift through it all, what is rising to the top is a discussion on composition vs. inheritance. For middle-tier work, I happen to think that composition works best. For UI work, I think inheritance works best. Of course this guideline is not absolute. There are many times in the UI side where I take advantage of composition. And, there are times in the middle tier where I take advantage of inheritance. I just happen to think that that needs of each tier are inversely proportional..

>John:
>
>This is really a silly argument. Inheritance is a nice feature, but you can survive with out it. When JAVA was developed there were no backward compatibility issues. The developers were free to begin from scratch. If inheritance were of no value, they would have left it out.
>
>I think MS purposely left inheritance out of VB to keep the language easy to learn. Inheritance can sometimes be more trouble than it worth. It takes a long time before you can realize the true benefit of this feature.
>
>Charlie