>Just a shot in the dark, but shouldn't it be:
>

>lcResponseCode = loEClient.GetResponseCode()
>

No, they are using an approach which I don't understand. I just told them that this methodology is quite weird. I should be able to call the method, as you mentioned, and expect it to return a string. But, don't ask me why, I have to define a variable first, pass that as a parameter and expect to receive an updated value in it after the method call. However, I just don't know how that could be achieved under COM.

If I call the method directly, as you mentioned, it'll say invalid parameter. So, I have to pass a parameter. If I pass a parameter which is not a variable, it says variable not found. So, I have to pass a variable that exists.

Note also that the VB code is not assigning the value to a variable but passing a parameter. That VB syntax is passing a parameter to the method. Otherwise, it would have been lcResponseCode=loEClient.GetResponseCode().

That method is already returning a value. It's a status 0 or 1 of the status of the method. I told them this is a weird approach. It shouldn't be done like that.