>Well you lost me after "it does the job". But if this foxISAPI supports regular HTTP methods (GET, POST and whatnot) there should be a way to get into the data portion. But I've never played with it.

Hey - your picture has dissappeared - and it was so becoming!:-)

I know it supports a URL like the ones in the browser address bar. I still have not determined if both GETS and POSTS are bar type URLs. With MSHTTP, we designate the GET or POST in an Open() method.

With ASP there is a request structure (oXML.load(request)). The MSXML is instanciated and the "load" (which is a "file" loader, not the string loader - noting the POST sent an XML string) embeds the XML.

I have not tried it - but I have begun to model a test solution. I don't know why I am so stuck ASP's "request" feature - it's required by any data, even URL parameters.

I am also bemused by the fact that the SERVER XML object retrieves the xml string as a file (Load). Maybe the client side setRequestHeader("Content-Type", "text/xml") actually provides a structure to let the server know that it is about to receive a parameter outside the POSTing URL. And maybe, like the URL formvars that are parked in a INI file, the requestheader indicates the data will be someplace other than the INI.

Hopefully, the XMLs my project will forward to the server may be small enough to pack the xml inside the URL.

BTW: Will SA's new Toyota plant be hiring independent contractors for any of their projects - or does "Harris Corp" already have them all tied up?:-)