ACC: Explicitly Close Recordsets to Help Prevent Database Bloat

ID: Q186311

The information in this article applies to:

Microsoft Access versions 97, 7.0

SYMPTOMS

Moderate: Requires basic macro, coding, and interoperability skills.

In the versions of Microsoft Access listed at the beginning of this article, if you use Data Access Objects (DAO) to open a recordset and don't explicitly close the recordset, DAO may hold onto the memory that it used for its previous compile until the next recordset is opened.

CAUSE

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.

RESOLUTION

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 subsequently reduce its size by compacting the database.

MORE INFORMATION

Microsoft provides programming examples for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and debug procedures. Microsoft support professionals 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 needs. If you have limited programming experience, you may want to contact a Microsoft Certified Solution Provider or the Microsoft fee-based consulting line at (800) 936-5200. For more information about Microsoft Certified Solution Providers, please see the following page on the World Wide Web:

http://www.microsoft.com/mcsp/

For more information about the support options available from Microsoft, please see the following page on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

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 demonstrate closing the Recordset and QueryDef objects using DAO.

Start Microsoft Access.

Open the sample database Northwind.mdb.

Copy the following code to a new module:


   The following sample code opens and closes a Recordset and a QueryDef
   object and displays both Recordset and QueryDef information in message
   boxes.

    Sub CloseObjects()
       Dim db As Database
       Dim rs As Recordset
       Dim qd As QueryDef

       Set db = CurrentDb
       Set rs = db.OpenRecordset("Employees", dbOpenTable)
       Set qd = db.QueryDefs("Invoices")

       rs.MoveLast ' Move to the last record in the Recordset.

       MsgBox "The Employees Recordset is open." & vbcr & _
          "The last Employee ID is " & rs![EmployeeID] & "."

       Msgbox "The Invoices query definition is open." & vbcr & _
          "The first field in the query is " & qd.Fields(0).Name

       ' Explicitly close the Recordset and QueryDef objects.
       rs.Close
       qd.Close
    End Sub

Run the CloseObjects subroutine.

REFERENCES

For more information about issues that can arise from leaving recordsets open in DAO please see the following articles in the Microsoft Knowledge Base:

Q164455 ACC: Problems Quitting Microsoft Access

Q164481 ACC97: Tips for Converting Applications to Using ODBCDirect

Additional query words: big bigger increase bloat bloated

Keywords : kbdta AccCon GnlOthr MdlGnrl MdlDao KbVBA
Version : WINDOWS:7.0,97
Platform : WINDOWS
Issue type : kbprb