Home |
Search |
Today's Posts |
#1
Posted to microsoft.public.excel.programming
|
|||
|
|||
Force particular Excel version loading with CreateObject?
Trying to figure out what the best way is to deal with the
problem of installing an .xla add-in when the user has multiple versions of Excel. My installation now works with COM automation in an INNO script. It all looks slightly different as INNO uses Pascal, but bascically it uses CreateObject. Now the question is how can I force a particular Excel version with CreateObject. I know that sticking the version number after Application doesn't work: CreateObject("Excel.Application.9") etc. I suppose the simplest and safest way is to just not automate this at all but tell the user to open Excel (of their choice) and do Tools, Add-ins etc. I am still hoping thought that there might be a way how to do this. Thanks for any advice. RBS |
#2
Posted to microsoft.public.excel.programming
|
|||
|
|||
Force particular Excel version loading with CreateObject?
Works OK if you explicitly write the addin registry keys for all versions
(no need to open Excel at all). regards Charles ______________________ Decision Models FastExcel 2.2 Beta now available www.DecisionModels.com "RB Smissaert" wrote in message ... Trying to figure out what the best way is to deal with the problem of installing an .xla add-in when the user has multiple versions of Excel. My installation now works with COM automation in an INNO script. It all looks slightly different as INNO uses Pascal, but bascically it uses CreateObject. Now the question is how can I force a particular Excel version with CreateObject. I know that sticking the version number after Application doesn't work: CreateObject("Excel.Application.9") etc. I suppose the simplest and safest way is to just not automate this at all but tell the user to open Excel (of their choice) and do Tools, Add-ins etc. I am still hoping thought that there might be a way how to do this. Thanks for any advice. RBS |
#3
Posted to microsoft.public.excel.programming
|
|||
|
|||
Force particular Excel version loading with CreateObject?
Yes, I can see it can be done via the registry, but for simplicity I
wanted to do it via COM. I suppose there just is no way to force the version that way. RBS Charles Williams wrote: Works OK if you explicitly write the addin registry keys for all versions (no need to open Excel at all). regards Charles ______________________ Decision Models FastExcel 2.2 Beta now available www.DecisionModels.com "RB Smissaert" wrote in message ... Trying to figure out what the best way is to deal with the problem of installing an .xla add-in when the user has multiple versions of Excel. My installation now works with COM automation in an INNO script. It all looks slightly different as INNO uses Pascal, but bascically it uses CreateObject. Now the question is how can I force a particular Excel version with CreateObject. I know that sticking the version number after Application doesn't work: CreateObject("Excel.Application.9") etc. I suppose the simplest and safest way is to just not automate this at all but tell the user to open Excel (of their choice) and do Tools, Add-ins etc. I am still hoping thought that there might be a way how to do this. Thanks for any advice. RBS |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Forum | |||
Createobject returns null in Excel | Excel Discussion (Misc queries) | |||
Templates not loading as xls version | Excel Programming | |||
How to force VBA to create an Excel.Application object of specified version of Excel? | Excel Programming | |||
Excel CreateObject on server | Excel Programming | |||
Why can't create Excel.Application using CreateObject? | Excel Programming |