I'm at my wits end with this bug.. I'm hoping this is so common, that
there is a very simple fix.

I have a C++ app that does COM based import/export of data directly
from Excel, but I have to think that anyone doing VBA would see this
all the time..

All of my calls to Excel to determine current workbook, how many
workbooks, current worksheet, how many worksheets, getting/setting cell
data all work wonderfully.. *unless* the user was editing a cell in the
worksheet..

If the worksheet is left in 'editing mode', almost all of the COM calls
will thow an exception, and not return successfully.

To get out of 'editing mode', I have tried everything from
SendKeys("ENTER") to closing the damn Workbook & reopening it (and
switching workbooks, activating, etc etc)

The machine either locks up, or just throws more exceptions.

I've meticulously gone through excel9.tli and excel9.tlh, looking for
some method remotely pertainant, such as a 'deactive' or 'end edit' or
anything that would allow the COM automation calls to succeed..

This is so very frustrating, because one very common user action in
Excel can bring (the functionality of) my whole app to its knees..

Any help/pointers/direction/solution would be greatly appreciated..

Thank You.



--
Pixeled
------------------------------------------------------------------------
Pixeled's Profile: http://www.excelforum.com/member.php...o&userid=26932
View this thread: http://www.excelforum.com/showthread...hreadid=401558