>
oword=CREATEOBJECT("word.application.8")
>?oword.Version
>12.0
>
>The CLSID for all versions that I see on my machine (12, 11, 8) is the same, {000209FF-0000-0000-C000-000000000046}. I have Word 2007 and 2003 on this machine (I assume that 2007=12 and 2003=11, logic be exiled), and would really like to have a way to test my recent automation thingy on both. Is there one? A way, I mean.
See if this helps:
http://support.microsoft.com/kb/292491A snippet:
A common perception for Office Automation when you have multiple versions of Office installed on a system is that you can dictate which version loads by using a specific version-dependent PROGID (for example, that "Excel.Application.9" loads Excel 2000, "Excel.Application.10" loads Excel 2002 and "Excel.Application.11" loads Office Excel 2003). However, this is not correct. Excel 2000 and later versions of Excel share the same CLSID, so the version that loads with these PROGIDs depends solely on which version was last installed.
For testing purposes, developers can force a specific version of an Office application to register by using the /regserver switch on the command line. For example, to force an Excel version to register without running setup, you can use a command line that resembles the following:
"c:\program files\microsoft office\office\excel.exe" /regserver
Although you can implement this switch for testing and development purposes, it is not recommended that you rely on this switch in production scenarios.
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"