>Thanks Rick for your help. I wanted to use server push because the server is receiving strings from the modem and I didn't want to risk overloading data if the client is not fast enough to retrieve it.
>
>If the server called a method of the client, passing the received string has a parameter, instead of assigning the string to the client property, would that have worked?

The problem is that you're trying to fire events which VFP is not capable
of no matter how hard you try to work around it <s>... (well actually there
are ways that you can do this by using a VB wrapper component to have it fire
the events on behalf of your VFP code).

Yes passing a value back to the client as a parameter should work as long as
the client is not busy. You see what happens is that yuo have two objects that
basically can't both be running simultaneously and passing messages to each
other through COM, because VFP basically treats it all as a single threaded
application.

+++ Rick ---


>
>TIA
>
>>Sure it can. Precisely because it is a COM object and COM supports accessing
>>methods and properties across all COM boundaries including over remote
>>machines.
>>
>>If you pass a ref to another object that object is fully functional.
>>
>>The problem Sylvain is seeing is not related to the object reference
>>but to the way he's trying to get at the property, which is more like
>>using events. Assign methods won't fire over COM at least not when you're
>>going the indirect route - meaning you never instantiated the original
>>object as a COM object - VFP is simply (well, actually not so simply)
>>marshalling a non-COM object as a COM object. In this process is where
>>the Assign problem occurs.
>>
>>The concept needs to be put on its head using client pull rather
>>than server push. The server should set a value on its own members
>>to be retrieved by the client which has a reference to the server.
>>That way you can bypass the circular references altogether.