>In this scenario, would automatic inheritance be nice? Sure, it would obviate the need for me to create an internal instance of the base class.
>
>Any way, that is the difference..

wow - for the first time I think I can actually see where implementation inheritance is valuable. But I had to go back & look up the definition for interface inheritance vs. implementation inheritance after this example just to keep from getting the lines crossed in the middle. So just to be anal...

Interface Inheritance - defines a new interface in the terms of one or more existing interfaces. This is what VFP inheritance is actually all about right?

Implementation Inheritance - defines a new implementation in terms of one or more existing interfaces. This is what the VB "implements" keyword is all about right?

And based on your example, the fact that VB does allow you to implement an interface... this is basically why Interface Inheritance as we VFP'rs know it isn't really all that important? This is actually starting to feel like "six of one half a dozen of the other" type deal now that I'm beginning to understand it better.