It looks as if you are using the service used by VS. This *may* work if you have VS active and have actually fired up the instance (for example by using 'View in Browser')
Test to see if the service can be accessed using that URL in a normal browser.
IAC, you will really need a proper instance of IIS to test this - there's no guarantee that VS will always use the same port number...

But, as Gary mentions, if using .NET is an option then it will be far more robust to do so with a VFP-friendly wrappper....


>Hi all,
>
>this if the first time I need to call a WebService from within a VFP program, and up till now it's not a happy experience.
>What I did up till now:
>I created a very simply WebService in VS2008 using C#. The only WebMethod in it is the standard 'HelloWorld'
>After some googling i found following code to call the WS from within VFP:
>
>LOCAL oTestWS as TestWS
>
>* Initialize the ASP.NET web service.
>loWS = NEWOBJECT("Wsclient",HOME()+"ffc\_webservices.vcx")
>loWS.cWSName = "TestWS"
>oTestWS = loWS.SetupClient("http://localhost:49780/Service1.asmx?WSDL","Service1", "Service1Soap")
>
>oTestWS.HelloWorld()
>
>Executing this code generates following error message: OLE error code 0x80070057: Unknown COM status code.
>It is the SetupClient command that invokes the error.
>
>What am I doing wrong ?
>
>Best regards,
>Hans