WD2000: Word Still Runs After Automation Session (212675)
The information in this article applies to:
This article was previously published under Q212675 SYMPTOMS
When you control Word from another application using Automation, as in the following example,
Sub WordTask()
Dim appWd As Object
Set appWd = CreateObject("Word.Application")
Set appWd = Nothing
End Sub
Word remains loaded in memory, even though the code uses the Set
statement to set the instance of Word to Nothing. NOTE: IF you press CTRL+ALT+DELETE to bring up the Windows Task List, you see that Winword is still running.
CAUSE
This behavior is by design. To quit Word when initiating an instance using Automation, you must use the Visual Basic for Applications Quit method, as described in the "Work Around" section of this article.
WORKAROUNDMicrosoft 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.
The proper method to use when ending a Word Automation session is to use the Quit method. For example:
Sub WordTask()
Dim appWd As Object
Set appWd = CreateObject("Word.Application")
' Quit the Word session.
appWd.Quit
' Set the Word OLE Object to nothing to free
' the appWd object memory.
Set appWd = Nothing
End Sub
Modification Type: | Major | Last Reviewed: | 6/17/2005 |
---|
Keywords: | kbdtacode kbmacroexample kbnofix kbprb KB212675 |
---|
|