VB has an Implements Keyword that allows you to implement an interface. Thats all that happens automatically - the interface gets inherited - not the functionality. The Class Builder in VB helps you through a lot of this - but quite a bit of code is generated and required to "simulate inheritance". I am not knocking it. After all, if that is your tool - and thats what you have to do - you do it. My argument was that to be OO, you should not have to write code to implement inheritance. We don't have to do it in VFP. Because of that, VFP is the standard to which I hold a lot of tools to, at least as far as implementing OO goes. Is it perfect? No. But it is pretty darn powerful.

If VB could come over VFP's way a bit more with respect to inheritance and containership, I really think there would be a lot of converts in our community tomorrow.



>>
>>The inheritance issue. Well, the time I spent over on DevX gave a good perspective on that whole issue. Yes, the way things in VFP are done with regard to inheritance is nice. But in all fairness to Karl, Zane, Kathleen, Phil, and the rest of the folks on DevX, they made a compelling argument for the way things are done in VB. The book I am reading and going through now - Professional VB 5 Business Objects - does a great job of illustrating how OO design principles can be implemented in VB. I did'nt think it was possible, but it is.
>>
>
>Excellent. I think inheritance in VB would be a big improvement. How do you go about doing it (I am just asking for a quick, summary-type response )?
>
>Thanks,
>Joe