But Michel, even in VB, using SET requires that the property already exists on the object, doesn't it? Or is this some feature of VB.NET of which I am unaware?

>>>>Would following work for you?

>>>>loHeaderHandler=CreateObject("SessionInfoClient.ClientHeaderHandler")
>>>>loUniversalThread.AddProperty('HeaderHandler',loHeaderHandler)
>>>

>>>
>>>The SOAP object is rejecting any use of AddProperty().
>>>
>>>It doesn't want us to attach anything to it. However, the SET syntax in VB works. There must be an equivalent in VFP.
>>
>>Michel,
>>
>>The HeaderHandler is a property of SOAP client object. Did you try?

>>loUniversalThread.HeaderHandler = CreateObject("SessionInfoClient.ClientHeaderHandler")
>>

>
>HeaderHandler is a member not found to the SOAP client directly. It has to be assigned such as the SET command in VB. The problem is that in VFP, that doesn't seem to be as simple. We first need to connect a property HeaderHandler to the SOAP client.