Hello Thom,

As I mentioned in another thread, the best solution is to call the web
service on your web server side (For example, in ASP script) and return
results to client. In this way, we don't need install any components on the
client side. We also can disable javascript on client browser and keep it
work.

If you want to call the web service directly on client side (for example,
in IE), there would be some limitation, for example, you must have SOAP
toolkit installed on client computer, and your client should enable
javascript and ActiveX.

Here is sample about soap toolkit and ASP:

http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q321512

Hope this help,

Luke

Hello Thom

I suggest you also can consider a component named "WebService Behavior". It
enables client-side script to invoke remote methods exposed by Web
Services, or other Web servers, that support the SOAP and Web Services
Description Language (WSDL) 1.1. Here is the link for it:

http://msdn.microsoft.com/library/default.asp?url=/workshop/author/webservic
e/webservice_node_entry.asp

Hope this help,

Luke