Forum Discussion

stukau's avatar
stukau
Copper Contributor
Jan 08, 2026

Database in an "inconsistent state" and other errors

Hello. I was directed here for help by Microsoft Tech Support because the problem is "file specific" and not at the app level. I am not computer savvy and have never used a forum like this. Tech support just kind of dumped me here and said "have at it," so any guidance, help, etc. would be appreciated.

I use Microsoft Office 365 as a personal/individual subscriber and my Access program started issuing error message over the past week. The biggest concern and problem is around db called Comic Books and I've attached the error message. When I click OK, it attempts to repair, fails and issues the second message. Another database--an earlier copy of Comic Books from mid December-- opens OK, but has its own problems, such as when I attempt to simply copy a table (see third error message). I don't know if these are related.  Can anyone help me? Is there any hope for me ever regaining access to the Comic Books database which was last accessible and working on January 4? Thank you. 

 

 

1 Reply

  • George_Hepworth's avatar
    George_Hepworth
    Silver Contributor

    Access is telling you the truth. This particular accdb has been corrupted and is no longer usable.

    The alternatives are trying to find a repair service which you can pay to recover as much of it as possible, or going back to the last previous working backup copy.

    Depending on what is in that database, the cost of a repair service might not be justifiable. If you decide to try that approach, check out https://www.everythingaccess.com/accessdatabaserepair_info.asp 

    Since you indicate that the most recent backup you have is also corrupted, you may have to go back to an even earlier saved backup, or perhaps it can be used to recover the objects that are not corrupted.

    Create a new empty accdb and try to import the tables, forms, reports, etc. from that partially working accdb. After each import check to see if is okay at that point, then proceed to the next. When you get to the point where an imported object doesn't work, or fails to import at all, you'll know where the corruption is.

     

    Good luck with the recovery.

Resources