VB has interface inheritance, which for middle-tier stuff, is all you really need. Most folks in the VFP camp find that when they take advantage of inheritance, it is in the UI. And, this maybe the most significant feature that makes VFP a better UI environment than VB.

On a middle tier basis, pure business logic, inheritance, from a code standpoint, is not a big factor. Inheriting interfaces OTOH, is a big issue, and one that VB does very well...

FWIW, you can "similuate" behavior and attribute inheritance with VB, just as you could with FPW 2.6....

>>ohhhhh be carefule Erik... Talk like that can get you flamed......<bg>
>>
>>>>It does make for an interesting topic - "What if VB got inheritance?????"
>>>
>>>If VB got inheritance, You just might see me jump ship for a bunch of projects. I would only use VFP for projects that wanted native data (that's still a lot).
>
>Isn't it true that there is a kind of inheritance. You setup a template function. When you use that template elsewhere, you have to fill in the details. Alan Griver was talking about it at the last So Cal Conference.