>James...
>
>It is really about addressing the continual questions of why VFP is not more popular since it supports implementation inheritance. A thoery I am putting out there is that folks outside the VFP world tend to rely on the composition for their middle-tier work. The middle-tier BTW, is the only context of this discussion.
>
>In the end, it is not about which tool is better as I don't think that question can be answered. In fact, I don't think that question does have an answer..
>
>
>>
>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.
><

I agree, John. But the point is, if I am developing middle tier components with VFP, I am going to use everything in my arsenal. If I'm doing the same with VB, the same applies. VB developers don't have all the advantages of OOP, so it doesn't matter to them because they don't know better. If VB supported inheritance and all the rest of the great tools that VFP has, you can damn well bet you'd see tons of subclassing on all the tiers.

If suddenly I became a VB developer and was forced to never use VFP again, I'd probably find a way to develop middle tier components without having to rely on inheritance and what have you, but, Boy, would I be hatin' life!