Hi,

>>
Its not quite the same. As I've just said in my last (long) reply before I read this, I can register the webservice but can't use it and I get an error object returned.
>>

Did you check the http address in the wsdl and try that in IE as I suggested ? (oh - and double check that the parameters are correct ; don't forget they are case sensitive)

>>
Don't know if I fully understood what the thread meant. Does it mean we are going to become more restricted by using VFP because it uses SOAP and we need to move to something using a .NET framework??
>>
The bit I noticed in that thread was the following:
"After all, Axis/Java Web Service toolkit needed to be downgraded to version 1.1 to make it work with MS SoapClient. To work with version 1.2 of Axis one may consider using PocketSoap 1.5 on a client which is Soap 1.2 compliant."

I don't think MS are going to produce any fixes/upgrades to the current MSSOAP toolkit so the implication is that if something doesn't work now there's not much point in waiting for a fix/enhancement. As suggested by the writer you could look at using PocketSoap instead of MSSOAP. (http://www.pocketsoap.com/pocketsoap/)

Regards,
Viv