Quote Originally Posted by Movian
Yes,
The instances that are created when done are set to visible to the user and then all programing interfaces are closed and or set to nothing as needed. The user edits the document, saves then closes word. HOWEVER sometimes (not every time) some times the word process will remain open after the user tells word to close. As i mentioned the MSACCess.exe process sometimes remains running after they close our database too. I don't believe there is a programing issue that is causing this as i have seen similar problems on machines not running our system.... I would be happy to look through possible causes, however at the moment i need to treat the symptom and see if i can locate these eroneous instances and close them.

Then i can look into possible causes further, i am not beoynd thinking my code may be causing it. However I do think that it may be a problem inside office itself....
I find that majority of the time this is cause by the code. What I commonly see is that coding issues do not cause any errors. But it does cause multiple instances to be created without you knowing. It is similar to variables when you do not not use Option Explicit. Unfortunately Option Explicit does not help with this issue.

Note: When Word does a mail merge with an .mdb/.accdb it always creates anothwer instance of Access. Even when using automation. This is a common cause of an MSACCESS.EXE left running but not visible when using automation. I find it best to avoid using an Access database as the merge source.