IMyObject IImplementedInterface_MyMethod1 IImplementedInterface_MyMethod2 IImplementedInterface Method1 Method1This will be listed under the Classes node as I described earlier. For more clarity, go up to http://www.mikeandkatherine.com/imp.jpg. This is what I'm seeing, and it's what I would expect. This implements IFoxChat from another VFP DLL. The methods I created in IFoxChat are GetText, LogOn, and SendText (the rest, as I'm sure you know, are standard COM methods that came along for the ride). If you look at the IFoxChat interface in the right pane, the methods are there. However, if I were to have expanded the methods node in the left pane, all I would see would be IFoxChat_GetText, etc., and the three methods listed above would not show up. Also, if I were to have expanded the Interfaces node in the left pane, all I would see would be the default interfaces (ISuperClass, etc.), and not the implemented interfaces in each class. This is all expected.
DEFINE CLASS SuperClass As Session OLEPUBLIC IMPLEMENTS Ifoxchat IN "chat_server.FoxChat" &&{263FA140-A732-490D-8F6F-0E30BE4ED6C6}#1.0 PROCEDURE Ifoxchat_LogOn(lsScreenName AS STRING) AS VARIANT * add user code here RETURN .t. ENDPROC PROCEDURE Ifoxchat_GetText(lsText AS STRING @, liLast AS Number @) AS VARIANT * add user code here RETURN 1 ENDPROC PROCEDURE Ifoxchat_SendText(lsText AS STRING) AS VARIANT * add user code here RETURN "Some text" ENDPROC ENDDEFINE> Is it possible that the Miami release doesn't do this correctly, or is it more likely that I am experiencing cerebral flatulence?