Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
How to instantiate older Word?
Message
De
02/02/2009 14:32:02
Dragan Nedeljkovich
Now officially retired
Zrenjanin, Serbia
 
 
À
02/02/2009 10:16:00
Information générale
Forum:
Visual FoxPro
Catégorie:
COM/DCOM et OLE Automation
Versions des environnements
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP SP2
Divers
Thread ID:
01378689
Message ID:
01378822
Vues:
15
>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.

And that common perception is probably a piece of FUD spread by the open source underground, I presume. Or was it actually published at some point by that fierce competitor of Microsoft, the insidious MSFT? How I'd love to give them a break... maybe send a brick and give them a break in a few windows.

Now with the new and improved search in UT, I can't search while I write, because both must happen in the same window... but I could swear (or was "curse" the proper expression?) that there was another MSKB article preaching exactly that perception.

Here: thread #1021593, thread #1269423.

>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
>


Don't know what's nicer, the disease or the cure. First they break their own code by having the latest registration overwrite the CLSID for any old version. It overwrote the CLSID for my Word 2000, even though it's absent for about four years now. Then they propose the cure in the style of "no we don't know how can you set the printer for this app, but you can set the system level printer while you use it and then revert when you're done - we're 100% positive you won't be printing from anything else while you're at it". I'm just whelmed...

The messenger is welcome, regardless :).

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform