Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Automation breaks with Office 2010 ClickToRun suites
Message
 
 
To
01/09/2010 19:14:20
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
01477460
Message ID:
01479745
Views:
70
The "Click-to-run" technology was originally designed as New Ways to Try and Buy Microsoft Office 2010. Later they decide to use it for full blown applications w/o considering consequences. Typical M$ way.

>Thanks Sergey and others for responding. I'm glad to know there is an alternative MSI install for the two Home versions of Office. But is it just me? Or is this silly that when you download the Office 2010 software there's no option right up front for which type of install you prefer and also what the considerations are (such as, do you use other software that interfaces with Office products?). This is creating more and more headaches where at first people can't figure out why their existing software doesn't work with their update to Office 2010. And then if and when they finally find out why, that they need to Uninstall Office and log back into where they downloaded it from and hunt for the Advanced download option to install the full version. To me, it seems the click-to-run is flawed due to this incompatibility with add-ons and other software, so it shouldn't be installed by default without an option up front and a blurb about some considerations before downloading and installing Office 2010.
>
>-Mark
>
>>The Home and Student and Home and Business Office 2010 suites can also be installed as regular applications. See http://support.microsoft.com/kb/982434/en-us
>>
>>>I can't find any posts on this, so I wanted to ask if anyone has any more info... Two of the three Office 2010 suites (Home and Student) and (Home and Business) use what MS calls "Click-to-run" technology. This technology does not install the office products normally as with 2007 and prior. Instead, it streams the installation components and runs the programs on a virtual Q: drive. Sounds ok, but the problem is that Automation code doesn't work.
--sb--
Previous
Reply
Map
View

Click here to load this message in the networking platform