This just gets deeper and deeper ;)

Using "xmldoc.selectSingleNode(xslPattern)" instead of 
"xmldoc.selectSingleNode(xslPattern)" does get rid of the VBscript error 
(but I don't know how it will work with real data whenever I figure out the 
permissions issue).

When I make that change, I now get my error messages as originally planned 
and the one I receive is "2146697209:No
data is available for the requested resource." However when I Googled that 
error, there was a MS PRB (http://support.microsoft.com/kb/281142) and when 
I did as they suggested

set xmldoc = Server.CreateObject("MSXML2.DOMDocument.3.0")
xmldoc.async = False
xmldoc.setProperty "ServerHTTPRequest", true
xmldoc.load(theResponse)

I still got an error, but this time it said "-1072896758:The character '>' 
was expected." I guess MS warning pages are not well-formed.

"Martin Honnen" <mahotrash@y...> wrote in message 
news:e2SQsGfjJHA.5732@T......
> Don Miller wrote:
>
>>     Function getNodeObject(theResponse, xslPattern)
>>         'if using 6.0 HAVE to use XPath instead of XSLPatterns
>>         'and would HAVE to include namespaces and prefixes in the xpath
>>         'for nodes associated with namespaces
>>         Dim xmldoc
>>         set xmldoc = Server.CreateObject("MSXML2.DOMDocument.3.0")
>> xmldoc.async = False
>>         xmldoc.load(theResponse)
>> errorMsg = xmldoc.parseError.errorCode & ":" & xmldoc.parseError.reason
>>         'set getNodeObject = nothing
>>         set getNodeObject = 
>> xmldoc.documentElement.selectSingleNode(xslPattern)
>
> The problem is that there is no documentElement when there is a parse 
> error so xmldoc.documentElement is nothing and you can't call 
> selectSingleNode or any method on nothing.
> Depending on the expression you are passing to selectSingleNode you might 
> simply be able to use
>           set getNodeObject = xmldoc.selectSingleNode(xslPattern)
> instead.
>
>
>
>
>
>
> -- 
>
> Martin Honnen --- MVP XML
> http://JavaScript.FAQTs.com/