You have to be more specific of what actually fails. Just call the ASP page and return a dummy SOAP (or any for that matter) response.

In your code below the classname should be quoted.

Check oXMLHTTP.responseText

to see what the server returns. Most likely an HTML error string of some sort.

BTW, you can use responseXML which returns a DOM object directly. You can then use oDOM.parseError.reason to check for errors in the XML and loading the first node and checking for the SOAP namespace to see if you actually got a SOAP response.

+++ Rick ---

>>>What are you doing with the data that comes back?
>
>If my memory servers me correctly, in the browser example I was experiementing with I was returning an XML string from the COM server via the responseText property, then loading it into the XMLDOM on the client where I bound it to the XMLDSO. It worked real well. That was a long time ago and unfortuneately I have lost the sample code.
>
>Today I was experiementing with something similiar except with a VFP client. The only real difference is this time, I was manually creating a SOAP envelope instead of an XML string with the method name and parms as elements. Problem is, nothing happens when I run the program. I tried using the script debugger, but I don't think the script is being run.
>
>*- Fox Client
>oXMLHTTP = CREATEOBJECT('Microsoft.XMLHTTP')
>oXMLHTTP.OPEN('Post', 'http://fineblumcb/web/listener.asp', .F.)
>oXMLHTTP.SetRequestHeader('SOAPAction', 'VFPserver.oRequest')
>oXMLHTTP.SetRequestHeader('Content-Type', 'text/xml')
>oXMLHTTP.SEND(BuildSOAPEnvelope())

Well, for one that's an invalid SOAPAction. SOAPAction should be URI#Method where the URI can be anything as long as it's unique. Not that it matters here.

>*- ASP
>*- Just enough to see if COM server instanitates
>cSOAPAction = Request.ServerVariables("HTTP_SOAPAction")
>Set oVFP = Server.CreateObject(cSOAPAction)
>
>Thanx,
>Charlie