>I still didn't have the time to try that out, but I must raise the point again: .NET doesn't use the same SOAP client as we've been using in VFP. Rather, it has its own native classes for doing that, which should be better as they are managed code. Although we can use the SOAP toolkit in .NET by means of COM interop, this isn't good, as we're paying the price of COM overhead (when we really shouldn't need it).

They might be better but they don't support all the functionalities of the SoapClient30. Using it by COM is the only way to make such a Web Service works presently.