Friday, July 20, 2012 5:08 PM
Is it possible to invoke a repair for Office 2003 and for Office 2010 programmatically?
If so, what would be the command(s) for performing each of these?
Sunday, July 22, 2012 7:37 AM
I did not know did I understand
In VBA you can invoke use cases
val(application.version)To Fix, you can use Control Panel/Programs/Modyf./Repair
Oskar Shon, Office System MVP
Press if Helpful; Answer when a problem solved
- Edited by VBAToolsMVP Sunday, July 22, 2012 7:40 AM
Monday, July 23, 2012 11:58 AM
To explain: some of our customers have both Excel 2003 and Excel 2010 installed on their machines. They will also have older and newer versions of our Excel Add-In -- the older version of this Add-In must run with Excel 2003, and the newer version must run with Excel 2010. There are reasons they would want to have both versions of our Add-In; they also have the ability to switch back and forth between our Add-In versions. But when they do that, they must switch which version of Excel is active (Excel.Application.CurVer).
So, we can detect when the Excel active version is not appropriate. We could just put up a long advisory message telling the user to please go to the control panel and manually repair Excel. But I would like to make it easier, by offering to the user the ability to start the repair for them. This is what I mean by "programmatically." It would not be starting the repair from VBA, but rather from an external program (could be a batch file, or a VB or C# project).
Hope that makes it more clear.
Monday, July 23, 2012 3:10 PM
I found the answer here for performing a repair via a Setup.exe command-line option:
- Marked As Answer by Anonymous9748 Monday, July 23, 2012 3:10 PM