Hi,

>im creating object with mssoap.soapclient30
>then calling a method with "TssVerify"
>soap.tssverify(inpservicecode,inpcompanyinfo,inpcustomerinfo,inpacctinfo)

when working with the high level interface I build each complex type into an xml string according to the documentation from wsdl.

inpservicecode = [<LocID>"9502"</LocID>] + ;                             
   [<Company>"xyz</Company>] + ;
   [<companykey>"6969"</companykey>] + ;
   [<email>"foo@mycompany.com"</email>]

When interfacing with the java/axis/tomcat world this is enough to carry parameters, but there might be other issues like custom session state via cookies or exception translation, which can be slightly different from MS-Soap behaviour.

I communicate via the low level interface, where you have the Serializer helping you to build your query XML. That way I am *also* able to work directly on the returned XML without automatic interference of the high level modules trying to interpret the return string.

Another way might be to redefine the WSDL locally <g>.

HTH

thomas