"Jason Burr" <JasonBurr@d...> wrote in message 
news:59CAE8B7-582E-4BA7-96E8-8562E106AD77@m......
> Joris,
>
> Sorry about that I did have the xsl included in the code I tried (just a
> typo when typing in here) sorry for the confusion. Anyway your right it 
> works
> with the snipped data that I posted. Turns out that the error was occuring
> much later in the full xml document when encountering an é character and
> thats the data I was testing with. I have had this issue alot and have no
> idea why when encoding is set to utf-8 that this would cause a problem
> usually I have control of the data source and replace any extended 
> characters
> like that but clearly thats not an option here any idea what to do to 
> resolve
> this?
>
> BTW the Microsoft.XMLDOM blows at reporting errors when I moved it all to
> client side stuff and declared an xsl in the xml document I got the proper
> error reported server side with the object just fails and makes no error
> report (even though an error catch is explictly called).
>
> Anyway any help on the extended character thing would be VERRRRYYYYY 
> helpful
> I guess its about time I figured out how to avoid eh???
>
> Thanks again,
>
> Jason
>
The usual cause is that the encoding is at odds with the declared encoding.

Joe (MVP - XML)