>>>Who said anything about DLL's?? Implements works with non-DLL classes in VB.
>>>As for implementing all the members in VB in a DLL, you are correct. In this
>>>context, I was talking about non-DLL implementations.
>>
>>Oh. If you're talking about non-DLL implementations, I guess you wouldn't be
>>interested in MSKB#Q305471 HOWTO: Use IMPLEMENTS with Microsoft Agent and
>>Visual FoxPro.
>I guess I am thick on this one. If all I want is event binding, I see VFPCOM
>saving me work that I would otherwise have to undertake using
>IMPLEMENTS/EventHandler. If OTOH, I need to deploy a VFP component in a COM+
>environment, then I would need to go to IMPLEMENT/EventHandler.

I'm not seeing that it actually saves work, assuming you drag-and-drop the interface. The VFPCOM version is more readable, but I like seeing all the return values out in front of me. I hate default properties, too. :-)

>As for the KB article you reference, how is that a non-DLL implementation?
>Isn't the agent a DLL?

Yes, it's a DLL - see the bold text above. I was just tossing it out as a for-what-it's-worth.