Access Database - Reports are corrupted

[Stacy Clark]

Hey Experts,

I am not able to open the Access database file. Can you guys please help me?

[#2]

Please share the exact error message that you are getting.

[#3]

@Robin Shanab 

here is the error message. 

[#4]

Try Compact and Repair and share the result.

[#5]

I am not able to open the file. How can I run compact and repair?

[#6]

Hi,

I'm not sure why you have "reports are corrupted" in the subject if you can't even open the complete database. However, the most common cause of this error message in the last 3.5 years is the MONSTER bug for which you can find the workaround here.

Servus
Karl
*********
Access-Entwickler-Konferenz: https://www.donkarl.com/?AEK
Access DevCon: http://AccessDevCon.com
Access FAQ: https://www.donkarl.com

[#7 · Accepted solution]

@Stacy Clark ,

You can check these references:
https://support.microsoft.com/en-us/office/access-reports-that-databases-are-in-an-inconsistent-stat...
https://www.stellarinfo.com/blog/access-database-in-inconsistent-state/

[#8]

I have 1 table and many reports in the DB. That's why I choose the title. Let me check the workaround, and I hope it will work for me.
thnx @Karl

[#9]

If that doesn't solve it, try decompiling your database to remove any corruption in compilation code. See http://www.fmsinc.com/microsoftaccess/Performance/Decompile.asp

In fact, I would try that first. It will only take a couple of seconds to do.

[#10]

Thank you so much to all the experts who replied here.
@Karl and @robin

[#11]

the db is already corrupt, so Don't ever try decompiling!
it will do much damage than good.

you need to re-instate your backup db.

[#12]

Any kind or repair carries a risk including compacting and decompiling. For that reason you should ALWAYS make a backup first.
However, I totally disagree with the comment that decompiling 'will do more damage than good'.

Decompiling will remove any corruption in your compilation code.
If that was the problem, it will be successful ...
...or if there is a different problem then it will have no effect

[#13]

Aside from making backups multiple times a day (I don't trust computers!), you could try creating a brand-new, empty MS Access ACCDB file and importing all your objects into it. I do that a few times a year with all my critical databases just to be sure no weirdness has crept in. Remember, MS Access applications are actually big ol' containers full of lots of different types of objects (forms, reports, tables, modules, etc). One bad bit in the container itself can make all your objects go bye-bye. I love working with Access, but I've learned not to trust it!

[#14]

Whilst that's another tool in any developers' arsenal, do bear in mind that its possible for problems in the original database to get transferred into the new database. I know as I've had that happen. For that reason, I would still suggest decompiling before importing into a clean database