The information in this article applies to:
SYMPTOMS
When you use the Step Into command to run a Visual Basic for Applications
macro line by line in the Visual Basic Editor, you may experience one or
all of the following:
CAUSEThese symptoms may occur when you use the Step Into command in the Visual Basic Editor window to run an automation macro that actives a Word dialog object from another application (for example, Microsoft Excel). The dialog box is not visible on screen, which causes the system to hang. The Microsoft OLE Automation extension loses focus of the application that is active in memory and does not activate the Word object on the screen. WORKAROUND
To cancel the message and restore system functionality on the Macintosh,
use the Force Quit command. To do this, follow these steps:
NOTE: If a dialog box is a part of your code, insert the breakpoint after the command. To do this, follow these steps:
STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. REFERENCESFor more information about getting help with Visual Basic for Applications, please see the following article in the Microsoft Knowledge Base: Q163435 VBA: Programming Resources for Visual Basic for Applications Additional query words: OFF98 vba
Keywords : kbdta macword98 |
Last Reviewed: August 13, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |