Quote Originally Posted by IanRyder View Post
Hi techgnome,



On that point, I totally agree with you. However, and even my own comments were probably not specific enough, this bit of XML:-

XML Code:
  1. <Properties xmlns="http://schemas.openxmlformats.org/officeDocument/2006/extended-properties" etc...>

effectively changed the Default Namespace to this string which then needs to be qualified to access the Child nodes.

I hope this helps to clear up the confusion.

Cheers,

Ian

BTW, I particularly liked the trick that AdamPanic2013 used in Post #7 to Import the Namespace. That was one that I did not know until now.
Ooooooh... I had to read that three times before I caught onto the namespace in the node... ok... what you said about it not being in the default namespace makes TOTAL sense now.... "If everyone would turn to page 42...."


Quote Originally Posted by ident View Post
New trick also, fails though here n:?

Code:
Dim v = d.<Properties>.<AppVersion>.Value
works

Code:
d.<AppVersion>.Value
Right...because Properties is the root document node... represented by d...
d doesn't hold the Properties node... it IS the Properties node.


-tg