Thanks for the information, Rick !


>Hi Tommy,
>
>I have a tool for accessing Web Services from FoxPro through .NET called the Web Service Proxy Generator. You basically point it at a Web Service WSDL document and it will create a .NET Proxy DLL and a FoxPro front end class that can call that proxy. The .NET proxy exposes the service methods as well as all of the related message objects and allows accessing the Web service through a class based interface.
>
>You can find more info, docs and a walk through video here:
>http://www.west-wind.com/wsdlgenerator/
>
>IAC, regardless of whether you use the proxy generator or not, I'd recommend using the .NET service clients and interop with them from FoxPro, as that's the most reliable Web Services client platform on Windows. All the COM tools - like the SOAP Toolkit have been deprecated years ago and unless the Web service is very simple they are very difficult to use with complex objects and especially arrays from FoxPro - especially if you need to pass these complex types.
>
>
>
>+++ Rick ---
>
>
>>Hey Gang!
>>
>>This question was posted earlier this morning in WEBSERVICES forum....
>>
>>Question
>>
>>We are needing to call a URL WebSevice from within Visual FoxPro.
>>
>>What do you recommend, COM Interop, ActiveX Component, .... ?
>>
>>Thanks