Posted this on TechHelp but not sure if it met the criteria:

When calling Word from Access VBA using a "Set wrdApp = New Word.Application" the instance created by Word includes the initial blank word document "Document1" (or some other next in line number).  Opening the document you wish to really manipulate with a "Set wrdDoc = wrdApp.Documents.Open(...)" still leaves that blank "Document1" hidden and open in the Word Documents collection.  When you close your document and quit the Word App (including setting the wrdApp and wrdDoc to Nothing AFTER you have used a Close on the Doc and a Quit on the App still leaves Word as a running process (because the "Document1" was never closed/cleaned from the Word Documents collection) according to the Windows Task Manager.  Is there some VBA code you can use to close the VBA instance of Word to not leave Word still running because of this blank hidden document when you use the New keyword in Set for Word? (Not shown on your taskbar BUT WinWord showing in Windows Task Manager and therefore consuming system resources).  Many users might be unaware this is happening.