Altova Mailing List Archives

Re: How to avoid the error XML_E_BADSTARTNAMECHAR

From: Peter Flynn <peter.nosp@-.--------.-->
Date: 8/3/2007 8:44:00 PM

Kevin LZJ wrote:
> Hi, all, 
>     We have such a problem that MSXML reports XML_E_BADSTARTNAMECHAR error. 
>     We have a fault-reporting system in which users can input remark 
> information freely. And the information is transferred to another system via 
> an interface program. In this interface program we use XML to enclose 
> fault-report information. We use MSXML to parse information from XML-format 
> data. However, because we permit users input information freely in some data 
> fields, we found that if users input '&' or some other special characters, 
> MSXML will report XML_E_BADSTARTNAMECHAR error, implying '&' character (and 
> some others) is not permitted in an XML field. 
>     So, is there any simple solution existing to avoid this situation, 
> besides we force users not input '&' character ? 

Pass the file or stream through a filter which replaces isolated & signs
with the XML equivalent, which is &amp;



These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.