Hi Charlie,

I should have been more clear. I know what the difference is between consuming and publishing a web service. So far, all I've done is consume them - and my problem is that I can't do so through our proxy server here at work. So I was a bit confused when you said something to the effect that you have to publish a web service before you can consume it.

My reference to intellisense was simply to underscore how easy it is to consume Web Services using VFP if the web service is registered with Intellisense (that is, if there are no firewall/proxy server issues to overcome ) - not to suggest that you need intellisense to consume a web service.


>>>I'm not sure I follow.
>
>When you publish a web service you are asking Fox to generate the WSDL (Web Service Description Language) file from a COM object in the application virtual directory on IIS. WSDLs are a lot like COM Type Interfaces in that they describe the methods and data types used in the web service. Applications wanting to consume the web service need to query this file. This is what the SOAP toolkit does.
>
>>>On my home box, where I am able to consume web services, all I do is click on tools - intellisense manager and then the 'types' tab and click on Web services to register a web service with intellisense.
>
>Intellisence has nothing to do with consuming a web service. All intellisense does if give you a visual reference to the web service type library so that you can more easily access its PEMs in code.
>
>Charlie