WD97: Word Still Running After OLE Automation SessionLast reviewed: February 11, 1998Article ID: Q161919 |
The information in this article applies to:
SYMPTOMSWhen you control Word for Windows 97 from another application 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 instance of Word to "Nothing").
NOTE: IF you press CTRL+ALT+DEL to bring up the Windows Task List, you will see that "Winword" is still running.
WORKAROUNDTo work around this problem, use the Quit method to close Word completely, as in the following example:
Sub WordTask()
Dim appWd As Object
Set appWd = CreateObject("Word.Application")
appWd.Quit
'Set the Word OLE Object to nothing to free the appWd object memory:
Set appWd = Nothing
End Sub
Microsoft provides examples of Visual Basic for Applications procedures 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. The Visual Basic procedures in this article are
provided 'as is' and Microsoft does not guarantee that they can be used in
all situations. While Microsoft support engineers can help explain the
functionality of a particular macro, they will not modify these examples to
provide added functionality, nor will they help you construct macros to
meet your specific needs. If you have limited programming experience, you
may want to consult one of the Microsoft Solution Providers. Solution
Providers offer a wide range of fee-based services, including creating
custom macros. For more information about Microsoft Solution Providers,
call Microsoft Customer Information Service at (800) 426-9400.
|
Additional query words:
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |