How to prevent database bloat after you use Data Access Objects (DAO) (289562)
The information in this article applies to:
- Microsoft Office Access 2003
- Microsoft Access 2002
This article was previously published under Q289562 Moderate: Requires basic macro, coding, and interoperability
skills. This article applies only to a Microsoft Access database (.mdb).
For a Microsoft Access 2000 version of this article,
see
209847. For a Microsoft Access 97 version of this article,
see
186311. SYMPTOMS A Microsoft Access database has begun to bloat (or grow
rapidly in size) after you implement Data Access Objects (DAO) to open a
recordset. CAUSE If you do not release a recordset's memory each time that
you loop through the recordset 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 need 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 running the
Compact and Repair utility (on the Tools menu).
Modification Type: | Minor | Last Reviewed: | 6/23/2004 |
---|
Keywords: | kbProgramming KbVBA kbprb KB289562 |
---|
|