Michel,

Did you try:

LOCAL loEClient
loEClient=CREATEOBJECT('MyObject')
? 'Response Code: ' + loEClient.ResponseCode


>>In this sample you have to use VBScript (VB code) to pass a variable by reference.
>>Either way I'm also very wondered why you do not get a result.
>
>I already tried passing it by reference. That didn't work.
>
>I talked again with them today. It is also a mystery for them as to know why the initial developer encapsulated the properties within the object forcing us to use a method to extract them.
>
>They also suggested me to pass it by reference but they never tried it and I also told them that this doesn't work.
>
>The situation right now is for them to do a special version which will include a wrapper method that we will call with a property which will be the name of the property to get the value which will be returned by the method. With about 10 lines, they should be able to do it. That's the easiest way we have found for that workaround. They are still investigating on it and will call me again later on this week.
>
>I also told them to look for Web Service. As this is something that goes across the net, they should consider that. Presently, they have to support various clients such as Perl, PHP, VB, VBScript, JScript, Delphi, ASP, etc. It costs them a fortune I guess for annual maintenance and support. I told them they could avoid worrying about the client and focus more on what they could offer thru a Web Service. I talked a lot to them about Visual FoxPro. They seems quite interested with what I said. I told them it could be so simple if they would just offer those methods thru a Web Service. The same would be true for us as well. Maybe they need some doc and demo of VFP 7.