VFP 7.0 will support the IMPLEMENTS keyword, and I assume that this would apply to COM objects as well. Until then, he'll be hard pressed to accomplish exactly what he wants. But I agree with you -- there may be design workarounds.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Well, you got me there. From your reply I understand you want to subclass an abstract class (interface only) that you have defined in a VB COM DLL.

Here you have basically created a COM class. But COM does not support that kind of inheritance, and my gut feeling tells me you can't do this. But then again, VFP is known to have the ability to sub-class ActiveX controls so my answer is I really don't know.

My question would be, why don't you define this class in VFP code? You can still expose it by creating a VFP COM DLL.