I think the lack of inheritance being a design feature that makes VB a better language is a MS party line or something like that.

I went looking for whitepapers comparing Frontends to SQL several years ago. There was one comparing VB to Powerbuilder on Microsoft.Com. The author took, from a consulting firm, took great pains to note that a selling point of PB was that it had inheritance. But his comment was that inheritance promoted poor s/w design and VB was better off without it.

PF

>I just got the new Software Development and I had to LOL while reading the departments listings. Bob O'Brien has a short article on "Simulating Inheritance."
>
>"You can easily compensate for VB's lack of inhereitance, but you might find that you're better off without it"
>
>In essence he says thay you could create a procedure file to hold all of your older version code in case you needed it.
>
>His closing lines are, "I've participated in several projects (using other languages) where relying too much on inheritance became a major problem. Visual Basic's Lack of inheritance helps limit such errors."
>
>That's what I love about Microsofts Flagship Product. They keep all the really hard stuff away from the people who could do the most dammage.