When you say you are creating a ServerObject, I'll assume you have the necessary information in the registry to go out and create this object on another machine. Either that or you need to use CREATEOBJECTEX() instead.

As for communications, AFAIK, this only results in two inter-object calls. The ServerObject receives a copy of your parameter object (via marshalling), performs its manipulations on the copy and transfers those changes back to your to the local Param object (via Unmarshalling) when the Execute method ends.

>I was reading an article on the use of parameter objects and I am unsure of a particular point. If my client sends a parameter object to my server, does each change to a parameter object property made by the server result in inter-object traffic?
>
>Example :
>***************
>oServerObject = CREATEOBJ('ServerObject')
>oParm = CREATEOBJ('ParameterObj')
>oParm.Value1 = 0
>
>* call server object, which changes the
>* value of the oParm.Value1 property.
>oServerObject.Execute(oParm)
>
>? oParm.Value1 && print new value
>
>***************
>
>Does this example create 2 inter-object messages?
> 1 for the create server object
> 1 for the oServerObject.Execute()
>or does it have 3 inter-object messages?
> above calls plus 1 for the Server Object modifing the Value1 property.
>
>Also.. is there anyway ( other then reading the code ) to monitor this traffic?
>
>TIA,
>
>Anthony