>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.

I saw Alan Griver's talk about using bridge patterns in VB. He said that using the Implements key word you could build a class like scenario. At the base you would build empty function calls. Then in your "sub-class", you would use the implements keyword this would add these empty function calls in the sub-class. You would have place the code inside of each of the calls. Kind of a backwards inheritance. I didn't know that VB even supported something like this.