Michel,

while I have no problem still using vfp whenever I find a suitable task, using SOAP via toolkit was one of the first things I dropped. Not knowing your special circumstances I caanot go into detail, but on the client side I use vfp earliest after XML is in a file. Server side, today other tools offer much more - down to installable demo kits auto-generated with tomcat sever into an ISO with bindings for java and dotnet in case of Axxis for instance. Newer ways to incorporate security and so on.

just my 0.0001€, as I have done a couple of vfp connected SOAP thingies..

thomas


>Is there any security we have to verify when using the SOAP Toolkit?
>
>I have two very basic commands:
>
>

>loWebService=Createobject("mssoap.soapclient30")
>loWebService.mssoapinit("http://www.myserver.com/WebService/WebService.asmx?wsdl")
>

>
>If I try that from the development environment to the development server, it works.
>If I try that from the development environment to the UAT server, it works.
>If I try that from the UAT environment to the development server, it does not work.
>If I try that from the UAT environment to the UAT server, it does not work.
>
>From DEV and UAT servers, the version of the SOAP Toolkit is the same.
>
>From the UAT server, if I try to execute those commands, I get:
>
>"Unexpected error OLE IDispatch exception code 0 from WSDLReader: WSDLReader:XML Parser failed at linenumber 0, lineposition 0, reason is: The download of the specified resource has failed. HRESULT=0x1: Incorrect function. - WSDLReader:Loading of the WSDL file failed HRESULT=0x80070057: The parameter is incorrect. - Client:One of the parameters supplied is invalid. HRESULT=0x80070057: The parameter is incorrect. .."