Article ID: 183872
Article Last Modified on 6/17/2005
APPLIES TO
- Microsoft Word 98 for Macintosh
This article was previously published under Q183872
SYMPTOMS
When you control Word from another program using OLE Automation, as in the following example
Sub WordTask()
Dim appWd As Object
Set appWd = CreateObject("Word.Application")
Set appWd = Nothing
End Sub
Word will still be loaded in memory (even though the code uses the Set statement to set the object variable to "Nothing").
WORKAROUND
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. The proper method to use when ending a Word OLE Automation session is to use the Quit method as in the following 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
MORE INFORMATION
For additional information, please see the following article in the Microsoft Knowledge Base:
181058 OFF98: How to Run Sample Code from Knowledge Base Articles
REFERENCES
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 vb vba vbe
Keywords: kbnofix kbmacroexample kbprb kbdtacode KB183872
