>>Check if https://yourserver.com/yourwebservice.asmx?wsdl is a valid url.
>Well lets just say that when I type in the url into the address bar of IE, I see some WSDL displayed in the browser.
>Is this an indication of a valid URL?

You should be able get the .wsdl via WinHTTP - did that when I had to access certificate secured sites which even protected the wsdl as well. Should take care of your immediate problem, since you can load the wsdl from a local path after fixing up the links inside.


I agree with Ricl that you should think about the tool to use for web services:
I also ran headfirst into "java problems" afterwards which were not directly solvable with the soap toolkit without some COM programming. I might have been able to use lower level COM components, but instead went with direct implementation
in vfp, as I had a very limited number of queries to process. Not generic, not beautiful,
but did the job. If you need something more generic/framework like, avoid the vfp soap toolkit
and either go for Rick's classes (perhaps replacing his WinINET based objects if he still uses them for WinHTTP if security is a moving target in the site you have to talk with) as a basis for your special needs or use .Net or even java.

You can write an adapter to any of these and keep you main app in vfp.

regards

thomas