WD2000: WithEvents Fails Quit Event with No Documents Open (212538)



The information in this article applies to:

  • Microsoft Word 2000

This article was previously published under Q212538

SYMPTOMS

When you use the WithEvents keyword to trap application events in Microsoft Word, you cannot trap the Quit event.

CAUSE

If no documents are open when you quit Word, Word does not generate the Quit event.

WORKAROUND

To work around this problem, have your Visual Basic for Applications macro create at least one document prior to quitting Word. The document can be a blank, empty document.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers 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 requirements.
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:

  1. On the Tools menu, point to Macros and then click Visual Basic Editor.
  2. In the Visual Basic Editor, click to select the Normal module.
  3. On the Insert menu, click Class Module.
  4. 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"0
       End Sub
    						
  5. In the General Declarations section of a module; for example, the NewMacros module, type the following declaration:
       Public cExit As New Class1
    						
    and the following procedure:
       Sub AutoExec()
          Set cExit.App = Application
       End Sub
    						
  6. Quit and restart Word to initialize the class.
When you quit Word again, the message box containing the Exiting Word prompt is displayed.

NOTE: If no documents are open when you quit Word, the Quit event is not generated, and the message box is not displayed.

For more information about Quit Event, in the Visual Basic Editor, click Microsoft Visual Basic Help on the Help menu, type Quit Event in the Office Assistant or the Answer Wizard, and then click Search to view the topic.

For more information about WithEvents, in the Visual Basic Editor, click Microsoft Visual Basic Help on the Help menu, type Public Statement in the Office Assistant or the Answer Wizard, and then click Search to view the topic.

For more information about how to use the sample code in this article, click the article number below to view the article in the Microsoft Knowledge Base:

212536 OFF2000: How to Run Sample Code from Knowledge Base Articles

REFERENCES

For additional 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


Modification Type:MajorLast Reviewed:6/17/2005
Keywords:kbbug kbcode kbmacroexample kbnofix kbProgramming KB212538