Sorry to come in again.

>In this case, we create an instance of the first class, and have implemented the same interface. In this case, there is only one method called MyMethod. If you change the behaviors of the ClassOne, those changes will be reflected in calls to MyMethod of ClassTwo.
>
>Now, is this subclassing? I would say no, it is not.
>Would I say, have we achieved the same end result? Yes,

Yes but you create a instances off all the parents.

In VFP you must only create a instance of the class you want to use . This is for me a major difference

You need to know in VB who are the parent's !

This scheme is ok when you have components ( complex objects ) as 'parent' class. So I think the VB OO is enought in a COM world but a can't really figure out to rebuild my applications that way.

I know you know it but I write it ... (Just to think out of the COM box ).


Every morning when a wake up I don't wan't to call and wake up all my familly to start my job.
Ok maybe I need to call my english teacher when I write english !

>
>I may not want to inherit the behaviors. I do however, want to keep the interface constant. In VFP, we really do not have a way of doing this.

Abstract class ?