Microsoft KB Archive/112630

{|
 * width="100%"|

-

The information in this article applies to:


 * Microsoft Excel for Windows, version 5.0
 * Microsoft Excel for Windows 95, version 7.0

-

SYMPTOMS
In Microsoft Excel, if you use OLE Automation to control another application, and if you display a dialog box from that application, the dialog box may not be correctly redrawn when you move it on the screen.

Also, if you switch to Microsoft Excel (for example, by pressing ALT+TAB) without dismissing the dialog box, Microsoft Excel may appear to hang. This is by design.

Dialog Box Is Not Redrawn Correctly
This error occurs because of the way in which dialog boxes are handled in OLE Automation. If you display a dialog box from another application, Microsoft Excel is temporarily "frozen" until the dialog box is dismissed. When Microsoft Excel is frozen this way, it does not have the ability to redraw parts of the screen that are occupied by a dialog box, and you may see "ghost" images of the dialog box that only disappear when control is returned to Microsoft Excel. The only solution to this problem is to not move dialog boxes that are shown by OLE Automation.

The redraw behavior used by Microsoft Excel is different than that used by Microsoft Visual Basic for Windows, version 3.0. Visual Basic version 3.0 has the ability to redraw parts of the screen, eliminating the "ghost" images, because of the way that Visual Basic handles dialog boxes that are shown by OLE Automation.

Microsoft Excel Hangs When a Dialog Box Is Displayed
Microsoft Excel cannot be accessed when a dialog box called through OLE Automation is still on the screen.

If you switch back to Microsoft Excel without dismissing the dialog box, an hourglass will appear and Microsoft Excel will appear to hang. If this occurs, you should switch to the dialog box by pressing ALT+TAB and dismiss the dialog box before returning to Microsoft Excel. Additional query words: lock up freeze doesn't respond

Keywords : kbprg

Version : WINDOWS:5.0,7.0

Platform : WINDOWS

Issue type :
 * }