>Craig - help me here - As far as I understand it - "interface" - at least as far as VFP is concerned and in practical terms - is the pool of public methods and properties. Since these methods/props are available (inherited) when I subclass - how is that not "interface inheritance"? If not - how does interface inheritance differ from the behavior I mentioned? In other words - if VFP had interface inheritance - what would it allow me to do that I can't now?

Interface Inheritance is a specific feature that allows your program to state in its type library that it supports one or more named interfaces. Interface inheritance in VFP 7 will be nothing more than a new keyword that instructs VFP to put the name of the interface in the tlb so that external entities can see that your classes support that named interface. To create a subscriber object for use with LCE, the subscriber must implement an interface named in the event class.

Currently all of the methods you create in a VFP COM server get packaged into a single default interface that is given the name of your object preceded with an I: IMyobject