Allen,
 I have been struggling with this very implementation, where I want
bi-directional communication between one server object and one remoting
client.  I have a SAO, whose methods are working properly when called from
the remoting client application, which runs on the same computer.  When I
add an event to the interface for the remoted class, the server object
raises the event, but the "listening" client never receives it.  The example
I based my event on, uses a second "Event Initiator" client, which simply
calls a "broadcast" sub on the server object.  The server object in turn
raises the event, and the "listening" client does receive the event.  I
can't seem to figure out why second "Event Initiator" client is needed, and
why the "listening" client, which has the event handler implemented, won't
work when the server object directly raises the event.  No exceptions
thrown.

Example1 - Client2 calls Svr.RaiseIt, which raises Event1, Client1 receives
Event1 successfully
Example2 - Svr directly raises Event1, Client1 does not receive Event1

Any ideas are much appreciated.

RJ