Issue in using win32com to access Excel file

The main reason for this attribute error is because your COM-server has shifted from late-binding (dynamic) to early binding (static).

In Late Binding, whenever a method is called, the object is queried for the method and if it succeeds, then the call can be made.
In Early Binding, the information of the object model is determined in advance from type information supplied by the object call. Early binding makes use of MakePy. Also, early binding is case sensitive.

There are two ways to fix this issue:

Use the dynamic module to force your code to work in a late-bound oriented way. Example use:
```
"win32com.client.dynamic.Dispatch()" instead of "win32com.client.Dispatch()" 
```
Use camelcase sensitive keywords for the early bound oriented way. Example use:
```
"excel.Visible()" instead of "excel.VISIBLE()" or "excel.visible()"
```

Try out

"win32com.client.dynamic.Dispatch()" instead of "win32com.client.gencache.EnsureDispatch"

As win32com.client.gencache.EnsureDispatch forces the MakePy process.

Renaming the GenPy folder should work.

It's present at: C:\Users\ _insert_username_ \AppData\Local\Temp\gen_py

Renaming it will create a new Gen_py folder and will let you dispatch Excel properly.

A solution is to locate the gen_py folder (C:\Users\\AppData\Local\Temp\gen_py) and delete its content. It works for me when using the COM with another program.

While I trust the previous answers better understand EnsureDispatch, if you came here because you have this problem but cannot amend your code, or do not want to, I was able to fix this problem by renaming a folder. Running these lines raised the same error:

from win32com.client.gencache import EnsureDispatch
import sys
xl = EnsureDispatch("Excel.Application")  # Error here
print(sys.modules[xl.__module__].__file__)

Now, unfortunately, if you get the error it's hard to know where that file is. For me it was this folder: C:\Users\<username>\AppData\Local\Temp\gen_py\. Appending an underscore to that folder name (or deleting it) should cause the folder to be re-created when the code is re-run.

hat tips to

https://www.pyxll.com/_forum/index.php?topic=436.0
https://gist.github.com/rdapaz/63590adb94a46039ca4a10994dff9dbe

The pyxll link has another block of code to call for potentially another folder location. I didn't use it so i'm not posting the code here. The fix above worked for me, but just in case you can go further down the rabbit hole.

If I want to make sure that python starts a new excel instance (for instance to access macros in my xlsm files), I use

xlApp = win32com.client.DispatchEx("Excel.Application")

That way I can close the application without hurting the instance that was already open.

Otherwise, I could simply use

xlApp = win32com.client.Dispatch("Excel.Application")

Does that work for you?

Issue in using win32com to access Excel file

Related

Recent Posts