Microsoft KB Archive/172181
Article ID: 172181
Article Last Modified on 1/20/2007
- Microsoft Word 97 Standard Edition
This article was previously published under Q172181
When you use the WithEvents keyword to trap application events in Microsoft Word, you cannot trap the Quit event.
If no documents are open when Word exits, Word does not generate the Quit event.
To work around this problem, have your Visual Basic for Applications macro create at least one document prior to exiting Word. The document can be a blank, empty document.
Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.
Microsoft provides programming examples for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and debug procedures. Microsoft support professionals can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific needs. If you have limited programming experience, you may want to contact a Microsoft Certified Partner or the Microsoft fee-based consulting line at (800) 936-5200. For more information about Microsoft Certified Partners, please visit the following Microsoft Web site:
For more information about the support options that are available and about how to contact Microsoft, visit the following Microsoft Web site:
WithEvents is an optional keyword for the Dim, Private and Public declaration statements. It is used to trap specific Application or ActiveX object events, and is valid only in class modules.
To create sample Visual Basic for Applications code that uses the WithEvents keyword, follow these steps:
- On the Tools menu, point to Macros and then click Visual Basic Editor.
- In the Visual Basic Editor, click to select the Normal module.
- On the Insert menu, click Class Module.
In the General Declarations section of the class module, type the following declaration
Public WithEvents App As Application
and the following procedure
Private Sub App_Quit() MsgBox "Exiting Word" End Sub
In the General Declarations section of a module, for instance the NewMacros module, type the following declaration
Public cExit As New Class1
and the following procedure
Sub AutoExec() Set cExit.App = Application End Sub
- Exit and restart Word to initialize the class.
When you exit Word again, the message box containing the Exiting Word prompt is displayed.
NOTE: If no documents are open when you exit Word, the Quit event is not generated, and the message box is not displayed.
For more information about WithEvents, from the Visual Basic for Applications Editor, click the Office Assistant, type Public Statement, click Search, and then click to view "Public Statement."
For more information about trapping events, click the Office Assistant, type events, click Search, and then click one of the following topics:
- Using Events with ActiveX Controls
- Using Events with the Application object
- Using Events with the Document Object
- Quit Event
- Open Event
- Auto Macros
NOTE: If the Assistant is hidden, click the Office Assistant button on the Standard toolbar. If Microsoft Help is not installed on your computer, please see the following article in the Microsoft Knowledge Base:
120802 Office: How to Add/Remove a Single Office Program or Component
For additional information, please see the following article in the Microsoft Knowledge Base:
173707 OFF97: How to Run Sample Code from Knowledge Base Articles
For more information about getting help with Visual Basic for Applications, please see the following article in the Microsoft Knowledge Base:
163435 VBA: Programming Resources for Visual Basic for Applications
Additional query words: wordcon vba vb vbe
Keywords: kbbug kbcode kbhowto kbmacroexample kbprogramming KB172181