Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
ACC2000: To Help Prevent Database Bloat, Explicitly Close Recordsets
Article ID: 209847 - View products that this article applies to.
This article was previously published under Q209847
Moderate: Requires basic macro, coding, and interoperability skills.
This article applies only to a Microsoft Access database (.mdb).
For a Microsoft Access 2002 version of this article, see 289562
In Microsoft Access, if you use Data Access Objects (DAO) to open a recordset and you do not explicitly close the recordset, DAO may hold onto the memory that it used for its previous compile until the next recordset is opened.
Because the recordset memory is not released, each time that you loop through code, DAO may recompile, using more memory and increasing the size of the database.
To avoid consuming unnecessary resources and increasing database size, use the Close method of the Recordset object to explicitly close the recordset's memory when you no longer require the recordset.
If the database has increased in size because you did not use the Close method of the Recordset object, you can reduce the size of the database by compacting it.
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. When you create a Recordset (or QueryDef) object in code, explicitly close the object when you are finished with it. Microsoft Access automatically closes Recordset and QueryDef objects under most circumstances; however, if you explicitly close the object in your code, you can avoid occasional instances when the object remains open. The following steps show you how to use DAO to close the Recordset and QueryDef objects.