>Tell you what, how about you folks give me a small problem to solve. The problem should be one where if you solved it in VFP, you would use inheritance. Then, I will take a stab and solve it in VB, all with out inheritance, and all without copying and pasting code...
>
>>>You mean two or more classes. This is no different than two or more subclasses. The commonly held myth is that when you don't rely on inheritance, you have to copy and paste code. That simply is not true.. The fact is, there is NO hierarchy. And, as far as the native stuff goes, look at what VFP, C++, and other tools do. It is all smoke and mirrors to a large extent.
>>
>>OK Mr. VB Wiz < s > I say it's time to turn the tables on your challenge just a bit. There's has been good examples presented & discussed now. You somewhat dared the general public to present examples of the other side of this issue that weren't contrived & we did. So how about you give us a VB example, that isn't contrived, that contradicts the copy-paste myth here?
>>
>>After all, for us folks who are only experienced with VFP, this myth as you call it apart of the natural process for those of us well accustomed to taking advantage of inheritance(and you think you said as much to Erik on another message).

John,

I am conviced it can be done in VB without inheritance. But who cares? I can do it VFP with inheritance, polymorphism and lots of OOP thongs! I use VFP and all the tools available to me. If I were using VB, I'd would have any OOP thongs.