Simple, but try removing the ";" after Void. VFP is not recognizing the MessageBox call. Let me know what happens after that.
>Alright Larry,
>
>The reason most people keep their good advice to themselves is that they know they'll be continually pestered for additional advice...
>
>I went back to my app, and reconstructed the interface class for the object who's events I wanted to monitor. I was very careful, and for all intents and purposes, it appears that VFP7 likes my code. The EVENTHANDLER() didn't blow up on me, and the app ran as I expected EXCEPT that the event-handling class's procedures don't seem to be firing. For instance, the object I'm monitoring has an event called 'IEICQueue2_ObjectAdded', and the handler has a procedure for this:
>
>PROCEDURE IEICQueue2_ObjectAdded(p_Queue AS VARIANT, p_Object AS VARIANT) AS VOID;
>
>
>I placed a simple MESSAGEBOX() command in the proc for troubleshooting, and it didn't get fired under normal circumstances. I then tried to force the procedure right after I created the event-handler:
>
>oQueue=CREATEOBJECT("ClientCOM2.EICQueue2")
>oQQ=NEWOBJECT("QQ")
>oQQ.IEICQueue2_ObjectAdded(1, 1)
>EVENTHANDLER(oQueue,oQQ)
>
>
>...where the class looks like this:
>
>
>DEFINE CLASS QQ AS SESSION OLEPUBLIC
>
>IMPLEMENTS IEICQueue2 IN "C:\PROGRAM FILES\INTERACTIVE INTELLIGENCE\CLIENTCOMLITEA.DLL"
>
> PROCEDURE IEICQueue2_ObjectAdded(p_Queue AS VARIANT, p_Object AS VARIANT) AS VOID;
> MESSAGEBOX("Added")
>ENDPROC
>
>
>
>ENDDEFINE
>
>
>
>Could you tell me why this is not firing interactively?
>
>Thanks a lot!
Larry Miller
MCSD
LWMiller3@verizon.netAccumulate learning by study, understand what you learn by questioning. -- Mingjiao