Why compact and repair access database

If database files distributed over a network and manifold users work openly with the file at the same time, then chances of corruption are very high.

Corruption risk somewhat increases if users edit data within Memo fields, and risk expands over time. You can alleviate this risk by utilizing Compact and Repair Database authority. Nevertheless, such corruption does create danger for the design of databases, like misplaced VBA code or impracticable forms.

Not often, database corruption results in loss of data. When the user begins changing data and gets disturbed in between—because of network loss — Access counts that file to be corrupted. The file could be fixed, but some data might go missing after completing the repair process. You can run the Compact and Repair tool to resolve database file corruption. If Access entirely fixes a corrupted file, it shows a message after completion and that you must check database contents to ensure that everything is the way you want.

Note: Database option can be set that involves the Compact and Repair Database command to operate automatically every time you shut a specific database. In numerous user databases, you may not wish to utilize this option, since it can temporarily dislocate database accessibility. Here are the things that you need to do:.

You can opt for Compact on Close database choice if you wish to automatically compact and repair Access database when it shuts.

As you add and update data and change its design, a database file becomes larger. Some of this growth comes from new data, but some comes from other sources:.

Access creates temporary, hidden objects to accomplish various tasks. Sometimes, these temporary objects remain in your database after Access no longer needs them. When you delete a database object, the disk space that the object occupied is not automatically reclaimed — the database file still uses that disk space, even though the object is deleted.

As your database file fills up with the remains of temporary and deleted objects, its performance can degrade. Objects may open more slowly, queries may take longer than normal to run, and typical operations generally seem to take longer. In particular circumstances, a database file can become corrupted. If a database file is shared over a network and multiple users work directly with the file simultaneously, that file has a small risk of becoming corrupted.

The risk of corruption is somewhat greater if users frequently edit data in Memo fields, and the risk grows over time. You can mitigate this risk by using the Compact and Repair Database command. Often, this type of corruption results from a problem with a Visual Basic for Applications VBA module and does not pose a risk of data loss.

However, this type of corruption does pose a risk of database design damage, such as lost VBA code or unusable forms. Rarely, database file corruption does result in data loss. Usually, this loss is limited to the last action of one user; that is, a single change to data. When a user starts to change data and the change is interrupted — for example, because of network service loss — Access marks the database file as corrupted.

The file can be repaired, but some data may be missing after the repair is complete. Protect data with backup and restore processes. Set General user options. Get started. Compact and repair a database. Need more help? Expand your skills. Get new features first. A subscription to make the most of your time.

Try one month free. Was this information helpful? Yes No. Summary: This blog describes the manual process to compact and repair Access database without opening it. It also mentions an Access repair tool that can help you fix the database when the compact and repair utility fails. Also, hardware or software failure, using databases with VBA module, and adding or deleting data in MEMO fields are a few other factors that may lead to Access database corruption.

When an Access database file turns corrupt or gets damaged, you may have a problem opening the database. To regain access to the database, you can try compacting and repairing it. Following are some actions you must perform before initiating the compact and repair operation:. After performing these actions, you can begin with the compact and repair operation. A copy of the compacted and repaired file will get saved in the exact location as your original database.