WD98: WithEvents Fails Quit Event with No Documents Open

Last reviewed: March 3, 1998
Article ID: Q181790
The information in this article applies to:
  • Microsoft Word 98 Macintosh Edition

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 Word exits, 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 exiting Word. The document can be a blank, empty document.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

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 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 needs. If you have limited programming experience, you may want to contact the Microsoft fee-based consulting line at (800) 936-5200. For more information about the support options available from Microsoft, please see the following page on the World Wide Web:

   http://www.microsoft.com/support/supportnet/refguide/default.asp

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"
          End Sub
    
    

  5. 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
    
    

  6. 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, click the Office Assistant while in the Visual Basic Editor, 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:

   ARTICLE-ID: Q179216
   TITLE     : OFF98: How to Use the Microsoft Office Installer Program

REFERENCES

For additional information, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q173707
   TITLE     : 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:

   ARTICLE-ID: Q163435
   TITLE     : VBA: Programming Resources for Visual Basic for
               Applications


Additional query words:
Keywords : kbdta kbdtacode kbmacroexample OffVBA macword98
Version : MACINTOSH:98
Platform : MACINTOSH
Issue type : kbbug
Solution Type : kbpending


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 3, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.