MS Access database in most cases, becomes inaccessible when an error message pops up during its mounting. This error message can be a result of network problems, system issues, or MS Access database corruption. While getting over from system and network problem is easy, repairing a corrupted database is difficult. Few main causes of MS Access database corruption are application malfunction, power outage, and virus infection. An easy way to overcome any database corruption is by restoring it from an updated backup. However, if no backup is available, then you can run an inbuilt repair utility 'Compact and Repair'. But if database corruption persists even after running the above utility, then you will need to use a commercial access repair application to repair your database.
To explain the above problem, consider a practical case where you create a table 'Accounts' with ten rows. Now, when you attempt to view the Autoincrement Id for a new record in Accounts table, the table displays less rows. It also displays a difference of rows in comparison to the original Accounts table. Furthermore, when you attempt to update the Accounts table, you encounter the below error message:
“Primary index is not unique”
Cause:
The above behavior occurs when the Accounts table is corrupted.
Resolution:
To isolate the above issue and repair the Accounts table, you will need to run 'Compact and Repair' utility. Below are the steps to use this repair utility:
1.Launch the utility and click on 'Tools' option.
2.Select 'Database Utilities' and click 'Compact and Repair Database' option.
3.Browse to the damaged MS Access database and select 'Database to Compact From’ option
4.Choose 'Compact' and click 'Save'.
Once the repair is complete, the Accounts table comes in reusable form. However, if the error message persists while accessing the Accounts table, then you will need to opt for a third-party access database recovery software. These Access Repair tools scan the corrupted database objects, repair them, and restore the repaired object at user-specified location.
Access Recovery ensures maximum repair of Access database objects, such as, tables, forms, and reports. The Access Repair utility supports repair of databases created in MS Access 2007, 2003, XP (2002), and 2000. Compatible with Windows 7, Vista, 2003, XP, and 2000, the read only software safely repairs the database without modifying the original database file.
To explain the above problem, consider a practical case where you create a table 'Accounts' with ten rows. Now, when you attempt to view the Autoincrement Id for a new record in Accounts table, the table displays less rows. It also displays a difference of rows in comparison to the original Accounts table. Furthermore, when you attempt to update the Accounts table, you encounter the below error message:
“Primary index is not unique”
Cause:
The above behavior occurs when the Accounts table is corrupted.
Resolution:
To isolate the above issue and repair the Accounts table, you will need to run 'Compact and Repair' utility. Below are the steps to use this repair utility:
1.Launch the utility and click on 'Tools' option.
2.Select 'Database Utilities' and click 'Compact and Repair Database' option.
3.Browse to the damaged MS Access database and select 'Database to Compact From’ option
4.Choose 'Compact' and click 'Save'.
Once the repair is complete, the Accounts table comes in reusable form. However, if the error message persists while accessing the Accounts table, then you will need to opt for a third-party access database recovery software. These Access Repair tools scan the corrupted database objects, repair them, and restore the repaired object at user-specified location.
Access Recovery ensures maximum repair of Access database objects, such as, tables, forms, and reports. The Access Repair utility supports repair of databases created in MS Access 2007, 2003, XP (2002), and 2000. Compatible with Windows 7, Vista, 2003, XP, and 2000, the read only software safely repairs the database without modifying the original database file.
No comments:
Post a Comment