Oops, my fault! (I'm embarrassed :-{  )

Under this condition, the DOM was being inadvertantly reloaded after the 
reference was set to that particular Element. So the Element was pointing to 
DOMRef #1 which wasn't referenced any more by m_XDOM which was now loaded 
with DOMRef #2. (Interesting how the original DOM is still hanging out in 
memory which leaves the Element reference as valid, it just doesn't happen 
to be pointing to the DOM which is referenced by m_XDOM. But it does make 
sense.)

Anyway, I think there's a valuable lesson here. If you have a Node or 
Element which is 'detached' from its underlying DOM, check to see whether 
that DOM has been reloaded since the reference was set, since this will mean 
that the DOM is actually no longer the underlying DOM for the Node or 
Element reference.

- Joe Geretz -

"Joseph Geretz" <jgeretz@n...> wrote in message 
news:OHWXjBEIFHA.2620@t......
> What am I doing wrong? I'm using SelectSingleNode to get a reference to an 
> Element in the DOM. Then I'm setting the attribute. m_XCert.Xml shows the 
> new data, but m_XDOM.Xml doesn't! How can this be? Isn't m_XCert a node of 
> m_XDOM??? I'm baffled!
>
>    Dim m_XDOM     As DOMDocument40
>    Dim m_XCert       As IXMLDOMElement
>
>    Set m_XCert = m_XDOM.selectSingleNode("certificate")
>    m_XCert.setAttribute "expires", Format$(Now + 5, "yyyymmdd")
>
> Thanks for your help!
>
> - Joe Geretz -
>
>