Thank you Viv - That't the only explanation I've heard that makes since. Your advice has already been implemented. When the XML (manifest) is transcribed to an ocxTreeView, a special routing traps and ignores it.

I thought it was a "bug" in DOMDocument - one of these days, its true purpose will be revealed!

Still the redundance is somewhat confusing [because]: the TITLE Node "Value" is also the content of #text.
>Hi,
>
>

><item identifier="INTRO" identifierref="RESOURCE_INTRO">
>      <title>Introduction</title>
></item>
>

>In the XMLDOM the text "Introduction" IS a node (i.e. a child node of title). The nodetype is NODE_TEXT and this type always has a nodename of '#Text'. If you have text present in an element it's always going to show up this way when you walk the DOM and the appearance of your treeview is technically correct. If you don't want these nodes to show up I suppose you could just remove these nodes from the document.
>
>Regards,
>Viv