Access closes app but process remains open

[Robert Ross]

I have to create a macro/module that can close Access
between uses. I have tried both macro's (RunCommand,
Quit) and Modules (DoCmd.Quit, etc.) and in all
circumstances, Access closes in the Application area, but
remains as an open process (Ctrl+Alt+Del, Processes).
This causes Access to hold the RAM required to store it's
information. Because of this, users begin to get Virtual
Memory errors since the instances of Access still open in
Processes hold that memory.

I have tried the following commands in modules to close
Access:
Unload Me
DoCmd.Quit

Application.Quit acQuitSaveNone

DoCmd.Quit acQuitSaveNone

I've even gone so far as to add a SendKeys statement in a
macro to send Alt+F4. Each time, Access closes the
application but keeps the process open.

Any ideas?

 

[Marshall Barton]

I have to create a macro/module that can close Access
between uses. I have tried both macro's (RunCommand,
Quit) and Modules (DoCmd.Quit, etc.) and in all
circumstances, Access closes in the Application area, but
remains as an open process (Ctrl+Alt+Del, Processes).
This causes Access to hold the RAM required to store it's
information. Because of this, users begin to get Virtual
Memory errors since the instances of Access still open in
Processes hold that memory.

I have tried the following commands in modules to close
Access:
Unload Me
DoCmd.Quit

Application.Quit acQuitSaveNone

DoCmd.Quit acQuitSaveNone

I've even gone so far as to add a SendKeys statement in a
macro to send Alt+F4. Each time, Access closes the
application but keeps the process open.

This the only thing that comes to mind:

http://www.mvps.org/access/bugs/bugs0005.htm