>>>>>What about this scenario,
>>>>>
>>>>>- Client Create Object A
>>>>>- Client Call an Object A Method
>>>>>- Object A Create Object B
>>>>>- Object A Calls an Object B Method
>>>>>- Object B Encounter an error
>>>>>- Object B Returns control to the client with ComReturnError()
>>>>>
>>>>>Object A will still be active and is not aware of the problem of Object B, So what append in this case ?
>>>>>
>>>>>
>>>>
>>>>Are you SURE control is being returned to the client?
>>>
>>>Yes i am 100% sure, Object B Returns control to the client without notifying Object A
>>>
>>>> How are you creating Object B?
>>>
>>>loSrv = CreateObject("Myserver.MyClass")
>>
>>I have to admit that this is not my area of expertise (so be forgiving), but I am learning a lot in this thread. In my tests, ComReturnError() in Object B triggers the Error method in Object A, which can then hand the error back to the client.
>
>Are you trying this on 2 COM Servers (MTDLL's) running on MTS Or COM+ ? My tests returns control to the client

No, both are COM EXE servers. I created Object A as a COM server from the VFP command window. If the results are different under MTS/COM+, I would definitely consider this a bug. After all, Object A is the client of Object B.