>I sent you some code and a screenshot of a class that implements the VBSAXHandler interfaces.

By design. You're seeing the same thing that was in the JPEG I posted on my site yesterday. The Interfaces node will only contain the default interfaces. In order to see the non-default interfaces, you need to expand the Classes node, then expand the interfaces node in the right pane.

Let's look at another typelib that wasn't generated by Fox. Open activeds.tlb (Active Directory Services) from the system directory. Open the Interfaces node. What, no IDispatch? Well, we know that can't be right, since many VFP devs use ADSI all of the time. Go back up to the classes node, expand it, and select a class. Expand the Interfaces node in the right pane. Ah, there's IDispatch, only it's just not the default interface (it's not in bold). So, basically, what you see in the Interfaces node of the left pane are only the default interfaces for that particular typelib, and an implemented interface is not a default interface.

Oh, BTW, I'm also willing to fall back on the fact that VB COM servers using IMPLEMENTS behave the same way. :-)