Office Supplemental Release (October 2009)
in [Word VBA]
|
From: Greg Maxey on 21 Dec 2009 20:27 Bill Coan passed me a link today containing information about change by MS that could affect how Content Controls interact with the XML datastore: The gist of the link is this: "Microsoft has released a supplement for Office 2007 (October 2009). The following patch is required for the United States. The patch will work with all Office 2007 languages. 2007 Microsoft Office Supplemental Release (October 2009) .img 12.9 MB After this patch is installed, Word will no longer read the Custom XML elements contained within DOCX, DOCM, or XML files. These files will continue to open, but any Custom XML elements will be removed. The ability to handle custom XML markup is typically used in association with automated server based processing of Word documents. Custom XML is not typically used by most end users of Word." Can this really be true!!?? Are all mapped CCs in existing docx and docm files now busted? Can one no longer map CCs to a CustomXMLPart? Why would MS do such a thing? My PC is setup to automatically download and install MS updates, but if the disaster described above is really true then apparently I don't have this release installed. I can still open a new document and run this code to create a CustomXMLPart Sub CreateTestXMLPart() Dim pXML As String ClearExcessXMLParts pXML = "<Test><Item>House</Item></Test>" ActiveDocument.CustomXMLParts.Add pXML End Sub Sub ClearExcessXMLParts() Dim i As Long For i = 4 To ActiveDocument.CustomXMLParts.Count ActiveDocument.CustomXMLParts(4).Delete Next i End Sub I can then save, close and reopen the file and access the CustomXMLPart using this code: Sub Testing() Dim oNode As CustomXMLNode Set oNode = ActiveDocument.CustomXMLParts(4).SelectSingleNode("Test/Item") MsgBox oNode.Text End Sub Looking for someone that is certain that they have installed the supplemental release and willing to try out the code above to determine the results and hopefully (very hopefully) confirm that CustomXMLParts can still be accessed. Thanks. -- Greg Maxey See my web site http://gregmaxey.mvps.org for an eclectic collection of Word Tips. Arrogance is a weed that grows mostly on a dunghill (Arabic proverb)
From: Jay Freedman on 21 Dec 2009 22:50 Hi Greg, The reason for this change is that MS lost a patent suit, described at http://blogs.zdnet.com/microsoft/?p=3712. Although the link at the Microsoft OEM Partner Center (http://oem.microsoft.com/script/contentpage.aspx?pageid=563214) says the patch is "required for the United States", the patch doesn't seem to be anywhere on the general downloads site, nor is it (yet) being sent out through Microsoft Update. I'm also not seeing any mention of this patch anywhere else on the web. Although it doesn't say so explicitly, I suspect that the patch is only being applied to newly sold copies of Office and not retroactively. Of course, that impression may be wrong, or MS may later be ordered to force the patch on everyone when the court catches on. Just so you know who to thank for this kick in the face, read http://www.itbusiness.ca/it/client/en/home/News.asp?id=55810. -- Regards, Jay Freedman Microsoft Word MVP FAQ: http://word.mvps.org Email cannot be acknowledged; please post all follow-ups to the newsgroup so all may benefit. On Mon, 21 Dec 2009 20:27:48 -0500, "Greg Maxey" <gmaxey(a)mIKEvICTORpAPAsIERRA.oSCARrOMEOgOLF> wrote: >Bill Coan passed me a link today containing information about change by MS >that could affect how Content Controls interact with the XML datastore: > >The gist of the link is this: > >"Microsoft has released a supplement for Office 2007 (October 2009). The >following patch is required for the United States. The patch will work with >all Office 2007 languages. >2007 Microsoft Office Supplemental Release (October 2009) .img 12.9 MB > >After this patch is installed, Word will no longer read the Custom XML >elements contained within DOCX, DOCM, or XML files. These files will >continue to open, but any Custom XML elements will be removed. The ability >to handle custom XML markup is typically used in association with automated >server based processing of Word documents. Custom XML is not typically used >by most end users of Word." > >Can this really be true!!?? Are all mapped CCs in existing docx and docm >files now busted? Can one no longer map CCs to a CustomXMLPart? Why would >MS do such a thing? > >My PC is setup to automatically download and install MS updates, but if the >disaster described above is really true then apparently I don't have this >release installed. > >I can still open a new document and run this code to create a CustomXMLPart > >Sub CreateTestXMLPart() >Dim pXML As String >ClearExcessXMLParts >pXML = "<Test><Item>House</Item></Test>" >ActiveDocument.CustomXMLParts.Add pXML >End Sub > > >Sub ClearExcessXMLParts() >Dim i As Long >For i = 4 To ActiveDocument.CustomXMLParts.Count > ActiveDocument.CustomXMLParts(4).Delete >Next i >End Sub > >I can then save, close and reopen the file and access the CustomXMLPart >using this code: > >Sub Testing() >Dim oNode As CustomXMLNode >Set oNode = ActiveDocument.CustomXMLParts(4).SelectSingleNode("Test/Item") >MsgBox oNode.Text >End Sub > > >Looking for someone that is certain that they have installed the >supplemental release and willing to try out the code above to determine the >results and hopefully (very hopefully) confirm that CustomXMLParts can still >be accessed. Thanks.
From: Greg Maxey on 22 Dec 2009 04:05 Jay, How does one say thanks for learning about a kick in the head ;-). Thanks. Is the ability to create and use a CustomXMLPart available in the Word2010 Beta? "Jay Freedman" <jay.freedman(a)verizon.net> wrote in message news:0ef0j5p2jvgfv6ie18im9hmcuf0o39pagj(a)4ax.com... > Hi Greg, > > The reason for this change is that MS lost a patent suit, described at > http://blogs.zdnet.com/microsoft/?p=3712. > > Although the link at the Microsoft OEM Partner Center > (http://oem.microsoft.com/script/contentpage.aspx?pageid=563214) says > the patch is "required for the United States", the patch doesn't seem > to be anywhere on the general downloads site, nor is it (yet) being > sent out through Microsoft Update. I'm also not seeing any mention of > this patch anywhere else on the web. > > Although it doesn't say so explicitly, I suspect that the patch is > only being applied to newly sold copies of Office and not > retroactively. Of course, that impression may be wrong, or MS may > later be ordered to force the patch on everyone when the court catches > on. > > Just so you know who to thank for this kick in the face, read > http://www.itbusiness.ca/it/client/en/home/News.asp?id=55810. > > -- > Regards, > Jay Freedman > Microsoft Word MVP FAQ: http://word.mvps.org > Email cannot be acknowledged; please post all follow-ups to the > newsgroup so all may benefit. > > > On Mon, 21 Dec 2009 20:27:48 -0500, "Greg Maxey" > <gmaxey(a)mIKEvICTORpAPAsIERRA.oSCARrOMEOgOLF> wrote: > >>Bill Coan passed me a link today containing information about change by MS >>that could affect how Content Controls interact with the XML datastore: >> >>The gist of the link is this: >> >>"Microsoft has released a supplement for Office 2007 (October 2009). The >>following patch is required for the United States. The patch will work >>with >>all Office 2007 languages. >>2007 Microsoft Office Supplemental Release (October 2009) .img 12.9 MB >> >>After this patch is installed, Word will no longer read the Custom XML >>elements contained within DOCX, DOCM, or XML files. These files will >>continue to open, but any Custom XML elements will be removed. The ability >>to handle custom XML markup is typically used in association with >>automated >>server based processing of Word documents. Custom XML is not typically >>used >>by most end users of Word." >> >>Can this really be true!!?? Are all mapped CCs in existing docx and docm >>files now busted? Can one no longer map CCs to a CustomXMLPart? Why >>would >>MS do such a thing? >> >>My PC is setup to automatically download and install MS updates, but if >>the >>disaster described above is really true then apparently I don't have this >>release installed. >> >>I can still open a new document and run this code to create a >>CustomXMLPart >> >>Sub CreateTestXMLPart() >>Dim pXML As String >>ClearExcessXMLParts >>pXML = "<Test><Item>House</Item></Test>" >>ActiveDocument.CustomXMLParts.Add pXML >>End Sub >> >> >>Sub ClearExcessXMLParts() >>Dim i As Long >>For i = 4 To ActiveDocument.CustomXMLParts.Count >> ActiveDocument.CustomXMLParts(4).Delete >>Next i >>End Sub >> >>I can then save, close and reopen the file and access the CustomXMLPart >>using this code: >> >>Sub Testing() >>Dim oNode As CustomXMLNode >>Set oNode = ActiveDocument.CustomXMLParts(4).SelectSingleNode("Test/Item") >>MsgBox oNode.Text >>End Sub >> >> >>Looking for someone that is certain that they have installed the >>supplemental release and willing to try out the code above to determine >>the >>results and hopefully (very hopefully) confirm that CustomXMLParts can >>still >>be accessed. Thanks.
From: Peter Jamieson on 22 Dec 2009 05:28 Your test code works in the (English) copy of the Office 2010 beta that I have here. Whether it will work in the final release doubtless depends on what happens in the courts. Sorry, I do not have the patch so cannot test that side of things. I don't know how MS's patching for OEMs works but I wouldn't be surprised to learn that this patch applies to Office/Word SETUP itself, not to a copy of Office already installed on a user's machine - if so, such a patch would not be for typical end users, only for admins who need to tailor SETUP. Peter Jamieson http://tips.pjmsn.me.uk On 22/12/2009 09:05, Greg Maxey wrote: > Jay, > > How does one say thanks for learning about a kick in the head ;-). Thanks. > > Is the ability to create and use a CustomXMLPart available in the Word2010 > Beta? > > "Jay Freedman"<jay.freedman(a)verizon.net> wrote in message > news:0ef0j5p2jvgfv6ie18im9hmcuf0o39pagj(a)4ax.com... >> Hi Greg, >> >> The reason for this change is that MS lost a patent suit, described at >> http://blogs.zdnet.com/microsoft/?p=3712. >> >> Although the link at the Microsoft OEM Partner Center >> (http://oem.microsoft.com/script/contentpage.aspx?pageid=563214) says >> the patch is "required for the United States", the patch doesn't seem >> to be anywhere on the general downloads site, nor is it (yet) being >> sent out through Microsoft Update. I'm also not seeing any mention of >> this patch anywhere else on the web. >> >> Although it doesn't say so explicitly, I suspect that the patch is >> only being applied to newly sold copies of Office and not >> retroactively. Of course, that impression may be wrong, or MS may >> later be ordered to force the patch on everyone when the court catches >> on. >> >> Just so you know who to thank for this kick in the face, read >> http://www.itbusiness.ca/it/client/en/home/News.asp?id=55810. >> >> -- >> Regards, >> Jay Freedman >> Microsoft Word MVP FAQ: http://word.mvps.org >> Email cannot be acknowledged; please post all follow-ups to the >> newsgroup so all may benefit. >> >> >> On Mon, 21 Dec 2009 20:27:48 -0500, "Greg Maxey" >> <gmaxey(a)mIKEvICTORpAPAsIERRA.oSCARrOMEOgOLF> wrote: >> >>> Bill Coan passed me a link today containing information about change by MS >>> that could affect how Content Controls interact with the XML datastore: >>> >>> The gist of the link is this: >>> >>> "Microsoft has released a supplement for Office 2007 (October 2009). The >>> following patch is required for the United States. The patch will work >>> with >>> all Office 2007 languages. >>> 2007 Microsoft Office Supplemental Release (October 2009) .img 12.9 MB >>> >>> After this patch is installed, Word will no longer read the Custom XML >>> elements contained within DOCX, DOCM, or XML files. These files will >>> continue to open, but any Custom XML elements will be removed. The ability >>> to handle custom XML markup is typically used in association with >>> automated >>> server based processing of Word documents. Custom XML is not typically >>> used >>> by most end users of Word." >>> >>> Can this really be true!!?? Are all mapped CCs in existing docx and docm >>> files now busted? Can one no longer map CCs to a CustomXMLPart? Why >>> would >>> MS do such a thing? >>> >>> My PC is setup to automatically download and install MS updates, but if >>> the >>> disaster described above is really true then apparently I don't have this >>> release installed. >>> >>> I can still open a new document and run this code to create a >>> CustomXMLPart >>> >>> Sub CreateTestXMLPart() >>> Dim pXML As String >>> ClearExcessXMLParts >>> pXML = "<Test><Item>House</Item></Test>" >>> ActiveDocument.CustomXMLParts.Add pXML >>> End Sub >>> >>> >>> Sub ClearExcessXMLParts() >>> Dim i As Long >>> For i = 4 To ActiveDocument.CustomXMLParts.Count >>> ActiveDocument.CustomXMLParts(4).Delete >>> Next i >>> End Sub >>> >>> I can then save, close and reopen the file and access the CustomXMLPart >>> using this code: >>> >>> Sub Testing() >>> Dim oNode As CustomXMLNode >>> Set oNode = ActiveDocument.CustomXMLParts(4).SelectSingleNode("Test/Item") >>> MsgBox oNode.Text >>> End Sub >>> >>> >>> Looking for someone that is certain that they have installed the >>> supplemental release and willing to try out the code above to determine >>> the >>> results and hopefully (very hopefully) confirm that CustomXMLParts can >>> still >>> be accessed. Thanks. > >
From: Greg Maxey on 22 Dec 2009 05:44 Peter, Thanks. Peter Jamieson wrote: > Your test code works in the (English) copy of the Office 2010 beta > that I have here. Whether it will work in the final release doubtless > depends on what happens in the courts. > > Sorry, I do not have the patch so cannot test that side of things. I > don't know how MS's patching for OEMs works but I wouldn't be > surprised to learn that this patch applies to Office/Word SETUP > itself, not to a copy of Office already installed on a user's machine > - if so, such a patch would not be for typical end users, only for > admins who need to tailor SETUP. > > Peter Jamieson > > http://tips.pjmsn.me.uk > > On 22/12/2009 09:05, Greg Maxey wrote: >> Jay, >> >> How does one say thanks for learning about a kick in the head ;-). >> Thanks. Is the ability to create and use a CustomXMLPart available in the >> Word2010 Beta? >> >> "Jay Freedman"<jay.freedman(a)verizon.net> wrote in message >> news:0ef0j5p2jvgfv6ie18im9hmcuf0o39pagj(a)4ax.com... >>> Hi Greg, >>> >>> The reason for this change is that MS lost a patent suit, described >>> at http://blogs.zdnet.com/microsoft/?p=3712. >>> >>> Although the link at the Microsoft OEM Partner Center >>> (http://oem.microsoft.com/script/contentpage.aspx?pageid=563214) >>> says the patch is "required for the United States", the patch >>> doesn't seem to be anywhere on the general downloads site, nor is >>> it (yet) being sent out through Microsoft Update. I'm also not >>> seeing any mention of this patch anywhere else on the web. >>> >>> Although it doesn't say so explicitly, I suspect that the patch is >>> only being applied to newly sold copies of Office and not >>> retroactively. Of course, that impression may be wrong, or MS may >>> later be ordered to force the patch on everyone when the court >>> catches on. >>> >>> Just so you know who to thank for this kick in the face, read >>> http://www.itbusiness.ca/it/client/en/home/News.asp?id=55810. >>> >>> -- >>> Regards, >>> Jay Freedman >>> Microsoft Word MVP FAQ: http://word.mvps.org >>> Email cannot be acknowledged; please post all follow-ups to the >>> newsgroup so all may benefit. >>> >>> >>> On Mon, 21 Dec 2009 20:27:48 -0500, "Greg Maxey" >>> <gmaxey(a)mIKEvICTORpAPAsIERRA.oSCARrOMEOgOLF> wrote: >>> >>>> Bill Coan passed me a link today containing information about >>>> change by MS that could affect how Content Controls interact with >>>> the XML datastore: The gist of the link is this: >>>> >>>> "Microsoft has released a supplement for Office 2007 (October >>>> 2009). The following patch is required for the United States. The >>>> patch will work with >>>> all Office 2007 languages. >>>> 2007 Microsoft Office Supplemental Release (October 2009) .img >>>> 12.9 MB After this patch is installed, Word will no longer read the >>>> Custom >>>> XML elements contained within DOCX, DOCM, or XML files. These >>>> files will continue to open, but any Custom XML elements will be >>>> removed. The ability to handle custom XML markup is typically used >>>> in association with automated >>>> server based processing of Word documents. Custom XML is not >>>> typically used >>>> by most end users of Word." >>>> >>>> Can this really be true!!?? Are all mapped CCs in existing docx >>>> and docm files now busted? Can one no longer map CCs to a >>>> CustomXMLPart? Why would >>>> MS do such a thing? >>>> >>>> My PC is setup to automatically download and install MS updates, >>>> but if the >>>> disaster described above is really true then apparently I don't >>>> have this release installed. >>>> >>>> I can still open a new document and run this code to create a >>>> CustomXMLPart >>>> >>>> Sub CreateTestXMLPart() >>>> Dim pXML As String >>>> ClearExcessXMLParts >>>> pXML = "<Test><Item>House</Item></Test>" >>>> ActiveDocument.CustomXMLParts.Add pXML >>>> End Sub >>>> >>>> >>>> Sub ClearExcessXMLParts() >>>> Dim i As Long >>>> For i = 4 To ActiveDocument.CustomXMLParts.Count >>>> ActiveDocument.CustomXMLParts(4).Delete >>>> Next i >>>> End Sub >>>> >>>> I can then save, close and reopen the file and access the >>>> CustomXMLPart using this code: >>>> >>>> Sub Testing() >>>> Dim oNode As CustomXMLNode >>>> Set oNode = >>>> ActiveDocument.CustomXMLParts(4).SelectSingleNode("Test/Item") >>>> MsgBox oNode.Text End Sub >>>> >>>> >>>> Looking for someone that is certain that they have installed the >>>> supplemental release and willing to try out the code above to >>>> determine the >>>> results and hopefully (very hopefully) confirm that CustomXMLParts >>>> can still >>>> be accessed. Thanks.
|
Next
|
Last
Pages: 1 2 3 Prev: Copiing styles to Normal.dotm Next: Using code to hide format of form field until needed. |