Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
ACC2000: Applications Run from Automation Do Not Always Close
Article ID: 210129 - View products that this article applies to.
This article was previously published under Q210129
Advanced: Requires expert coding, interoperability, and multiuser skills.
This article applies to a Microsoft Access database (.mdb) and to a Microsoft Access project (.adp).
When you open other applications, such as other Microsoft Office 2000 programs, through Automation code, the applications that you open may not always close when your code finishes running.
Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements. You can use Automation code to open and manipulate other Microsoft Office programs. When you open a program by using Automation, an instance of the program is created in memory. If you don't close each instance of a program that you open, that instance may remain open but hidden. Each time that this happens, additional memory resources are consumed on you computer until you either restart the computer or shut down the hidden instances of the program manually. Having multiple, hidden instances of a program in memory can adversely affect the performance of your computer.
To prevent multiple, hidden instances of a program started with Automation code from getting stuck in memory, explicitly close each instance of the program when you finish working with it. You can explicitly close an instance of an Office 2000 program by using the Quit method at the end of your Automation code. The following Office 2000 applications support the Quit method:
Converting from Microsoft Access 2.0In Access 2.0, the Quit method needed to be enclosed in brackets to work.
When you convert a database that uses the Quit method in this fashion from Access 2.0 to Access 2000, you will need to manually remove the brackets from the Quit method. The brackets will not cause an error, but if they are present, the Quit method will not close the instance of the program being run.
Steps to Manually Shut Down Hidden Instances of Programs
Windows 95 and Later
Steps to Reproduce the ProblemWARNING: Running this sample code will leave hidden instances of Excel running in your computer's memory. You will have to follow the steps listed under the "How to Manually Shut Down Hidden Instances of Programs" section earlier in this article to close these instances. Leaving hidden programs running in your computer's memory could affect your computer's performance.
The following code opens an instance of Excel and a sample file, but fails to explicitly close the instance. When the function is finished, the instance of Excel is still in memory.
For more information about programming with Automation, in the Visual Basic Editor, click Microsoft Visual Basic Help on the Help menu, type Understanding Automation in the Office Assistant or the Answer Wizard, and then click Search to view the topic.