Article ID: 824271 - View products that this article applies to.
This article applies only to a Microsoft Access database (.mdb).
Novice: Requires knowledge of the user interface on single-user computers.
For a Microsoft Access 2002 version of this article, see 304701
For a Microsoft Access 2000 version of this article, see 306204
For a Microsoft Access 97 version of this article, see 306829
In a Microsoft Office Access 2003 database, corruption in your database may occur for a number of reasons. This article contains a list of references to Microsoft Knowledge Base articles that may help you to resolve corruption in your database.
Troubleshooting and Preventing Database CorruptionThe following Knowledge Base article contains the troubleshooting steps that Support Professionals follow when they try to recover a corrupted database.
For additional information about troubleshooting and about repairing an Access database, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/283849/ )How to Troubleshoot and Repair a Damaged Access 2002 or later Database
Additional Troubleshooting ResourcesThe following Knowledge Base article may be of additional assistance to you in troubleshooting problematic database files.
For additional information about troubleshooting fatal errors, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/825444/ )How to troubleshoot fatal system errors in Access 2003 when Access 2003 is running on the Windows 2000 Operating System
Data RecoveryAfter you complete reading the troubleshooting articles that are listed earlier in this article, even if you still cannot recover your database, your data may be recoverable. There are a number of third-party companies that specialize in data recovery.
The following companies are known to specialize in data recovery. You may be able to find additional companies that specialize in this area by searching the Internet.
For additional information, visit the Action Front Data Recovery Labs Web site:
http://www.actionfront.com/For additional information, visit the PK Solutions Web site:
http://www.pksolutions.com/For additional information, visit the OfficeRecovery.com Web site:
http://www.officerecovery.com/access/index.htmMicrosoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information. The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
Technical Support from Microsoft Support ProfessionalsMicrosoft Support professionals can help you walk through the steps that are included in the referenced articles. Although Support Professionals can help you troubleshoot your database, Microsoft cannot guarantee that an Access database can be recovered or that data can be recovered during this process. Because a Support Professional will be working with your database, support of this nature is considered Advisory Services level support.
Contacting Advisory ServicesMicrosoft Advisory Services is an hourly fee-based, consultative support option that provides proactive support beyond your break-fix product maintenance needs. This is a remote, phone-based support option that includes working with the same technician for assistance with issues like product migration, code review, or new program development. This service is typically used for shorter engagements, and is designed for developers and IT professionals who do not require the traditional onsite consulting or sustained account management services that are available from other Microsoft support options. For information on Microsoft Advisory Services, refer to this Microsoft Web site:http://support.microsoft.com/gp/advisoryservice
Article ID: 824271 - Last Review: August 12, 2005 - Revision: 2.3