>>>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.
>
>Only knowing this from brief use, you can inherient the INTERFACE of a VB object, but not the IMPLEMENTATION... so, the Inherited Object is basically a template of methods but if you use it, it will have no functionality, until you implement it.
>
>Any corrections or expansions of this are welcome.
>
>BOb

This allows several classes to share the same interface. But, lets each class define it's own implementation of the interface.