BUG: VB Hangs While Automating Excel Using OLE ControlLast reviewed: March 4, 1998Article ID: Q181889 |
The information in this article applies to:
SYMPTOMSYour application hangs while automating Microsoft Excel 97 via the OLE control.
CAUSEThis problem occurs while automating a Microsoft Excel 97 object that is using in-place activation in an OLE control. The problem does not occur with all methods or properties. This problem has been reported with the following method/properties in the Microsoft Excel object library:
PrintOut Delete RESOLUTIONA workaround is to not activate the object while running the automation code. However, if you need to activate the object, do so in a separate window instead of using in-place activation. For example, this line activates the object in a separate window:
OLE1.DoVerb vbOLEOpenAnother workaround is to deactivate the object before calling the automation code that causes Visual Basic to hang. For example, the PrintOut and Delete methods cause this problem to occur. Before using these methods, you can deactivate the object prior to calling the method, then optionally reactivate the object after calling the method. See the MORE INFORMATION section later in this article for an example.
STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATION
Steps to Reproduce Behavior
|
Additional query words: locks freezes crashes
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |