Automation - task still running

Question

After Getting or Creating the Word object in my Access Automation procedure, doing my stuff and then Setting all the objects to Nothing at the end, I have two instances of Winword running as tasks. This occurs either way - after a GET or a CREATE action.

Should setting objects to Nothing kill off the task? If not why not and how should I ensure the tasks get killed?

Answer

From: Shamil Salakhetdinov <shamil@marta.darts.spb.ru>
Subject: Re: Automation - tasks still running
Date: 26 February 1999 10:52

Neil,

You have to call Quit method of Word Automation object before you set its
reference to Nothing:

dim appWord as new Word.Application
....
appWord.Quit
set appWord = Nothing

HTH,
Shamil