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 .md...
- 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/
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/
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.- The question isn't if the user who gets the error users Windows 10, the question is "do you have any users that Access the database who are running Windows 10?". If you have even a single user who is on Windows 10, then this error is likely due to this bug.
The only way to know for sure is to implement the workaround, compact and repair the database, and wait and see. If you keep having issues after C&R, then you need to start looking at the typical sources of corruption, things like unstable/saturated networks, wan/wireless network usage, unsplit database/shared front-end, ...I'm using Windows OS 11, MS Office Pro 2021.
In tables, when I try to create a data type field for "Lookup", I get this error. All other data types seem to function properly. This error is in all my databases.
I've tried Compact & Repair; Checked for updates; even did a reinstall. But nothing yet seems to work. I tried contacting tech support - which is totally useless and a waste of time.
Can someone please give me assistance on how to resolve this?
Thanks
- 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
