Hank:

If this web service can be consumed by a .NET Client, then it just a matter of using the WebServices importer from .NET Extender for VFP. It will create a DLL Assembly, that you can use as if it was a local object from VFP.

Because .NET Extender use all the .NET Stuff for dealing with the WebService, you really are using .NET from VFP.

Here is the a screenshot for the WebServices importer

>There could be any number of issues here. The Soap Header might be looking for authentication; the payload mighty need to be escaped; the payload might be a structure that VFP can't handle. It all depends... As usual.
>
>If all else fails, he can create a .Net solution, and then run it in VFP using etecnologia.net's VFP Extender for .Net. Creating the service in .Net is a Wizard-affair, and for some .Net services is the only practical solution. It all depends. <s>
>
>I have no idea whether VFP can handle the WSDL given: but remember that the SOAP toolkit, which VFP uses, is deprecated. And even though your friend is using WW stuff, Rick himself has recommended using .Net to create the services in many instances, rather than VFP (it's all on his prolific and useful blog).
>
>Hank
>
>>I have a friend who is trying to get webservices to talk to fox 9.0. He's come to me for help, but, since I don't use fox anymore and haven't used 9.0, I can't help him. Can someone provide me their email address for a couple of questions from him?
>>
>>
>>Here's his specific message:
>>
>>I'm trying to connect to this web services ( http://support.debisys.com/soap/webServices.wsdl ) through FoxPro 9 with no success. I'm trying to use the West Wind stuff, but I'm open to any suggestions.
>>
>>It can connect to the web service in .Net without a problem. Do you have any simple sample code that I could use to get this bugger working?
>>
>>
>>
>>
>>Thanks in advance.