MS SOAP Toolkit 3 is no longer supported by MS, but it NEVER
worked right. The unresolved built-in bugs have to do with
incorrect namespaces added to the SOAP envelope however the
message is constructed.
TCPMon will demonstrate this unequivocally.
Rummage around on the list archive and look for the .NET
alternatives, assuming you have to go MS.
HTH,
Elaine
Nicklas Karlsson wrote:
Forgive me if this is a little non-axis but somebody here has probably
worked with the MS SOAP Toolkit 3 before...
I added my first <xsd:dateTime> attribute to my complex type and the
call from Excel results in a
"Generic Custom Type Mapper: Element foo could not be loaded while
loading type Bar"
I understood from the documentation that dateTime had a mapping to the
VB date type. Surely I dont have to write
a custom type mapper for a date(?)
Thanks in advance,
Nik
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Where liberty dwells there is my country.
---- Ancient Latin phrase ----
