Mark Wilson I am the creator of TopXML. I am available for international and local (Australia) contracts. I am a Solution Architect/Business Analyst. I have worked in IT in several countries (NZ, Australia, South Africa, UK) building and training teams for government and very large non-governmental organizations. I am ex-Microsoft Consulting Services. I wrote the first book on Microsoft XML published in 2000 called XML Programming with VB and ASP. Most recently I have been building tools for the SEO industry. Ask me for a 37 point SEO health-checkup for your website.
First posted :
03/24/2008
Times viewed :
708
parseError
Is a member of:
XML DOM Document
Syntax
set objXMLDOMParseError = objDOMDocument.parseError
Remark
This property is read-only. This property returns an
XMLDOMParseError
object. The returned object is always a valid object. When you
are dealing with the DOMDocument interface, it inherits the
XMLDOMParseError interface; therefore all the properties of the
XMLDOMParseError object are exposed in the DOMDocument object
(for example, the parseError property). This means you can
interrogate any errors immediately after you have loaded your
DOMDocument, without having to set an XMLDOMParseError
object.
Example
In the following example, we demonstrate using the reason
property of the XMLDOMParseError object from the DOMDocument
object.
If objDOMDocument.parseError.reason <> ""
Then
'there has been an error with the loaded XML - show the
reason
MsgBox objDOMDocument.parseError.reason
End If
However, if you want to interrogate any errors in any of the
other types of Nodes, you have to get the XMLDOMParseError object
to find any of the error properties:
Set objXMLDOMParseError = objXMLDOMElement.parseError
If objXMLDOMParseError.reason <> "" then
Msgbox objXMLDOMParseError.reason
end if
This manuscript is an abridged version of a chapter from the
Manning
Publications book XMLProgramming with VB and ASP. This chapter
looks at the Microsoft DOM objects. NOTE: Most images have been
removed to increase speed and many of the code comments have also
been removed for presentation. Please purchase the book to enjoy
the full experience of all the chapters with images and code
comments!