Database bloat is not stopped by compacting database with Access 2002 format (810415)
The information in this article applies to:
This
article applies only to a Microsoft Access database (.mdb).
Moderate: Requires basic macro, coding, and interoperability
skills.
SYMPTOMSIf you have a database that is in Access 2002 format,
database bloat occurs when you repeatedly add or remove large numbers of
objects that contain code. You cannot stop the database bloat when you compact
the database.CAUSERecords are added to the MSysAccessStorage system table when
objects that contain code are created and the project is then compiled. Some of
these records remain when the objects are deleted. These records are not
removed when the database is later compacted.WORKAROUNDTo work around this problem, use either of the following
methods: Method 1After you remove objects that contain code, create a new
database and then import all the remaining objects from the original database
to the new database. Method 2If possible, develop the database by using Access 2000
format. Then, when the database is ready to deploy, create a new Access 2002
format database and import all the objects from the Access 2000 format
development database to the new Access 2002 database. Note Whether you use Method 1 or Method 2, when objects are imported
to a new database, the new database project must be compiled and then saved. If
references other than the defaults are used, they must be modified in the new
database. For additional information, click the following article
number to view the article in the Microsoft Knowledge Base: 205608
ACC2000: References Not Imported with Objects from Another Database
STATUS Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
Modification Type: | Minor | Last Reviewed: | 8/3/2004 |
---|
Keywords: | kbtshoot kbRepair kbsetup kbprb KB810415 kbAudDeveloper |
---|
|