CODEWITHSUNDEEP
pythonwindowsexcelwin32com
sam
sam

Reputation: 101

How to choose the version of excel which win32com.client has to use in python?

I have an excel 2007 file(*.xlsx) which is to be opened through a python script. But the problem is I have two versions of MS office (2003 and 2007) installed in my computer. Although I tried to make Excel 2007 as the default application to open xlsx files, the win32com.client is trying to open my xlsx file using Excel 2003. Also this is reverting back Excel 2003 as the default application.

Is there a way to force the win32com.client to choose Excel 2007 to open xlsx files?

Upvotes: 10

Views: 7069

Answers (4)

Bleeding Fingers
Bleeding Fingers

Reputation: 7129

The following should work since I have tested it although not with two versions of Excel simultaneous installed but instead forcing Excel files to open up in Word (aka WINWORD.exe). Replace the path to whichever version of Excel you want to be used:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\.xlsx]
"Content Type"="application/vnd.openxmlformats-officedocument.spreadsheetml.sheet"
@="Excel.Sheet.Custom"
"PerceivedType"="document"

[HKEY_CLASSES_ROOT\.xlsx\Excel.Sheet.Custom]

[HKEY_CLASSES_ROOT\Excel.Sheet.Custom\shell\Open]
@="&Open"

[HKEY_CLASSES_ROOT\Excel.Sheet.Custom\shell\Open\command]
@="\"C:\\Program Files\\Microsoft Office\\Office14\\EXCEL.EXE\" /dde"

[HKEY_CLASSES_ROOT\Excel.Sheet.Custom\shell\Open\ddeexec]
@="[open(\"%1\")]"

[HKEY_CLASSES_ROOT\Excel.Sheet.Custom\shell\Open\ddeexec\application]
@="Excel"

[HKEY_CLASSES_ROOT\Excel.Sheet.Custom\shell\Open\ddeexec\topic]
@="system"

Save the above reg script after replacing C:\\Program Files\\Microsoft Office\\Office14\\EXCEL.EXE with the path to the actual EXCEL.exe you'd like to use as default(be careful with the \\s), in a you_name_it.reg and run/merge/double-click it. It will ask you for confirmation, give it an affirmative and check.

Upvotes: 3

Caleb Hattingh
Caleb Hattingh

Reputation: 9235

I have not tried this, but perhaps you could launch the Excel version you want using something like 

desired_excel_path = 'C:\\Program Files\\Microsoft Office\\Office14\\EXCEL.EXE'
file_path = 'C:\\myfile.xlsx'

subprocess.call([desired_excel_path , file_path])

(or whatever is the subprocess method of launching Excel manually that works) and thereafter try

wb = win32com.client.GetObject(file_path)

to obtain the running instance.

Upvotes: 2

pekapa
pekapa

Reputation: 891

Have you tried to load the module via EnsureModule?
The usage is:

from win32com.client import gencache
mod = gencache.EnsureModule('clsID', 'lcID','versionMajor', 'versionMinor')

And you can retrieve all those needed from python makepy.py -i available in the lib/site-packages/win32com/client folder
It will open a window where you can select the application you want. You'll find both Excell versions in there, select the desired one and it will return how to connect it to python.



From here you will have two options.
1) excel = mod.Application should give you the Application dispatch but you might not be able to see the attributes from it (but the version should be the right one and commands should work as usual).

2) excel = win32com.client.Dispatch("Excel.Application") should use the module you just generated (but I'm not sure if this will work and bring the right version!).

Upvotes: 0

Raffi
Raffi

Reputation: 3396

For Excel 2013, you can type:

o = win32com.client.Dispatch("Excel.Application.15")

since the program is located somewhere like:

C:\Program Files (x86)\Microsoft Office\Office15\EXCEL.EXE

Since I do not have any other version installed, I guess it works if you just replace the 15 by the version you need. You can see the path of the binary that is launched by the command with eg. process explorer.

EDIT: This is impossible "Programmatically" :(

After having tried this:

excel15 = win32com.client.dynamic.Dispatch("Excel.Application.15")
excel14 = win32com.client.dynamic.Dispatch("Excel.Application.14")

which yields objects like this:

>> print excel15
<COMObject Excel.Application.15>
>> print excel14
<COMObject Excel.Application.14>

only one instance of Excel (14) is visible in process explorer. Doing 

excel15.Visible = True

confirms that.

It turns out that using automation for controlling both versions of Excel is impossible. Checking the Registry, the programs (Excel.Application.14 and 15) share the same CLSID. An there is only one LocalServer per CLSID (HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{00024500-0000-0000-C000-000000000046}\LocalServer on my computer). This LocalServer points to the last installed version, Excel14 (trial) on my computer. This is the only object created by the Dispatch call.

All this is explained here (§ "Using Automation to Control Microsoft Excel").

There is hope

As I said, this LocalServer points to the last installed version. There is hence a chance you can achieve what you want:

  • either you feel confident to change the registry by hand. I would say "easy" (change the application pointed by LocalServer, and the default application of the Excel.Application entry), but I will prefer the following simple solution
  • reinstall the 2007 application (of course, if you can). This is a poor/inelegant yet simple fix.

Upvotes: 6

Related Questions