Possible to Upgrade from Office 2003 SBE to Office Pro 2003 ???

[Symbeont]

I recently designed a .Net application for a client that uses Word's XML
capabilities and custom XML schemas to insert data. I find that when I try
to open/save a Word document in Office 2003 SBE that the custom schemas are
stripped out of the document. Also, I cannot install the MS Word XML ToolBox
utility for Word either, and later found out that it requires 2003 Pro or
Word stand alone editions. In addition, the docs out there on exactly WHAT
xml support is offered between the versions is extremely nebulous.

Why the heck MS strips out XML techologies from some versions of 2003 and
not others, yet promotes XML as a core reason for 2003 upgrades is completely
ridiculous. I'm a huge MS groupie, but this is the kinda stuff that arms
the MS nay-sayers.

Ok, done ranting. Does anybody know of a way to upgrade MS Office 2003 SBE
to MS Office Pro 2003? Please tell me this can be done relatively cheap....I
don't even need Access...just all the "real" XML support in the Office apps.

Thanks for any help with this...

Randy

 

[Bob Buckland ?:-\)]

Hi Randy,

Unfortunately moving laterally between editions of the
same Office version (in this case 2003 series) is considered
a crossgrade, rather than an upgrade and isn't supported
within the Office 2003 upgrade packages.

If the Office 2003 SBE is an OEM copy (sold with the PC)
then you may be able to arrange for a tradein/upgrade with
the PC supplier.

If the Office 2003 SBE is a retail copy and new, there is
a 30 day money back guarantee from MS on it that would let
you then acquire an Office 2003 Professional Edition.

The standalone Word 2003 package could be the least pricey
way to go it appears at present, otherwise.
http://microsoft.com/office/howtobuy
It's not yet clear if the MS Works Suite 2005 edition will have the
standalone Word 2003 with full XML capability. If so, then
historically MS Works Suite has been priced less than MS Word
standalone.

From the MS Word website on the additional capabilities in
standalone MS Office Word 2003 and MS Office 2003 Professional
Edition's copy of Word:

<<Note In all Office 2003 Editions, Word 2003 documents and Excel 2003 spreadsheets can be saved in a native XML file format which
can be manipulated and searched using any program that can process industry standard XML. With Office Professional Edition 2003,
companies can also use customized XML formats-or schemas-to enable easier and more advanced information creation, capture, exchange,
and reuse.>>


For additional information on using XML in Office family apps you may
also wish to visit the Office XML newsgroup
news://msnews.microsoft.com/microsoft.public.office.xml

===========
I recently designed a .Net application for a client that uses Word's XML
capabilities and custom XML schemas to insert data. I find that when I try
to open/save a Word document in Office 2003 SBE that the custom schemas are
stripped out of the document. Also, I cannot install the MS Word XML ToolBox
utility for Word either, and later found out that it requires 2003 Pro or
Word stand alone editions. In addition, the docs out there on exactly WHAT
xml support is offered between the versions is extremely nebulous.

Why the heck MS strips out XML techologies from some versions of 2003 and
not others, yet promotes XML as a core reason for 2003 upgrades is completely
ridiculous. I'm a huge MS groupie, but this is the kinda stuff that arms
the MS nay-sayers.

Ok, done ranting. Does anybody know of a way to upgrade MS Office 2003 SBE
to MS Office Pro 2003? Please tell me this can be done relatively cheap....I
don't even need Access...just all the "real" XML support in the Office apps.

Thanks for any help with this...

Randy>>
--
I hope this helps you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 explained
http://microsoft.com/uk/office/editions.asp

 

[Symbeont]

Thanks for the informative post Bob. I figured that would be the case, and
that a stand alone Word would be the cheapest option. I still fail to see
the philosophy of stripping the XML support out of SBE though, given that SBE
and PRO cost roughtly the same (one with Contact Manager and the other with
Access) and they both include .Net Programability Support install options.
Just doesn't make any sense...

Thanks again