By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,996 Members | 1,343 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,996 IT Pros & Developers. It's quick & easy.

win32com and Excel

P: n/a
Hi there,

I am accessing Excel's functionality via COM, by using the
win32com extention.

This works somewhat:
If I run it from the 'IDLE' editor, I get frequent hangs or errors.
Sometimes the app hangs, and Excel then waits indefinately for a COM
operation completion.
Sometimes, I get errors about properties not being writable (which
realy are writable).
I then need to kill excel en python stuff, and try again. Sometimes
it works, sometimes I get in a corrupt state.
Running without the IDLE environment, I get much better results.

After checking the file, I deciced to add a
OnQuit() to my event handler. Strangely enough, OnQuit events are only
sent for MS-Word, and not MS-Excel.

Is this an ommission in win32com, or in MS Excel itself? I cant find a
mention of OnQuit in the Visual Basic script help files.

I would like to discern between the closing of a workbook, and the
closing of the entire excel app.


Bram Stolk

Bram Stolk, VR Engineer.
SARA Academic Computing Services Amsterdam, PO Box 94613, 1090 GP AMSTERDAM
email: br** Phone +31-20-5923059 Fax +31-20-6683167

"Software is math. Math is not patentable."
"Software is literature. Literature is not patentable." -- slashdot comment
Jul 18 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.