Forum Discussion
Solved
Trouble finding the trigger behind the "Unrecognized database format Access" error message?
We have multiple local users on my domain (around 6), accessing a Access Front End database split.
For most of the days, things go well, but sometimes, after some user updates some register, the .mdb file becomes corrupt, and everybody else using Access on their local PCs get the "Unrecognized database format" error message (see picture). So I have to restart the server, erase the .ldb temporary file and then click on "Compact and restore database" option under Database Tools tab. That fixes the problem.
Microsoft 365 Access Build 16.0.3....
But what's the trigger? Is it a limitation of Access? Is there any way I can prevent this from happening?
Thanks in advance!
- If you are running on Windows 10 PCs then you are most probably facing
https://www.devhut.net/2018/06/13/access-bug-database-is-in-an-unrecognized-format/
I have a complex database with the tables sitting on a Server 2012 and mixed Windows 10/11 front-end users.
When I get this issue, I found that copying the data tables down to a Windows 11 machine, repairing it then putting it back on the server works.
- If you are running on Windows 10 PCs then you are most probably facing
https://www.devhut.net/2018/06/13/access-bug-database-is-in-an-unrecognized-format/- Hi Daniel,
I want to discuss this issue here because, I never get this type of error.
I saw many forums about this error, many experts says it is a bug. Now the question is; user only get this error in Windows 10?
I don't think so. Can it be related to corruption?
It's an open discussion, anyone can participate.Hello Daniel
I developed 4 ms access applications and spreaded the front end to users. From time to time I face the error (unrecognizable database format). I unplug the network and then backup and then restart my server. Then I compact and repair the database and then relinking the tables from the front end before sending it out again to users. In my opinion this error could possibly happen due to the difference between Microsoft access and windows version. I started to make users PCs as the serever to get More compatibility. All windows 10 and All Microsoft office 2016. I still have few PCs to change and hopefully this could possibly be more helpful. Anyway I'll share my experience.
- As a matter of fact, the last 2 times it happened, a win 10 Client PC triggered the server error. I'll take a look
