RE: Get Processing Instruction MSXML3.0 sp1

match="processing-instruction('MSSQLError')|processing-instruction('MSRT
SError')" works as a match expression in XSLT, so I would assume that
selectSingleNode("processing-instruction('MSSQLError')") would work.
Note that the MSRTSError is used by custom errors you might throw from a
stored procedure.

> -----Original Message-----
> From: Jay Gardner [mailto:jgardner@xxxxxxxxxxxxxxxxxxxxxx]
> Sent: Thursday, May 17, 2001 2:36 PM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject:  Get Processing Instruction MSXML3.0 sp1
> 
> Hello all,
> 
> I am having a little trouble with SQL Server 2000 XML capabilities.
> 
> I am using templates and sending the template a parameter for the sql
> statement.  The query can generate an error if an incorrect value is
> sent.  Normally this will not happen, but if it does I want to parse
> the XML returned from SQL Server.
> 
> Here is a sample error from SQL Server:
> 
> <?xml version="1.0" encoding="UTF-8" ?>
> <root xmlns:sql="urn:schemas-microsoft-com:xml-sql">
>   <?MSSQLError HResult="0x80040e14" Source="Microsoft OLE DB Provider
> 	for SQL Server" Description="Syntax error converting from a
> character
> 	string to uniqueidentifier."?>
> </root>
> 
> I am using the MSXML3 parser on a W2 server, and I am having a hard
time
> 
> gaining a reference to the processing instruction MSSQLError.  I have
> been
> trying to use selectSingleNode("//MSSQLError") but have had no luck.
> 
> Is there a way gain access to the processing instructions using an
XPath
> query?
> 
> Thanks,
> 
> Jay Gardner
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list