Access Database is getting corrupt again and again

Anonymous
2018-06-01T17:47:41+00:00

We have an application which was working okay till last month. But after the last windows update our clients are getting issues with access database. access database got corrupted.  We ran compact and repair. But it still getting corrupted again and again.  This issue started right after the window update. clients are on different OS. Like server 2018, server 2012 and windows 10.

Is there anything i have check in new windows update or any other step to prevent database corruption?

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

604 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-07-09T21:42:50+00:00

    I am having the same issue , access database in "inconsistent state" since last 1 week. It shows the message that database is in inconsistent state, will attempt to recover. During this, a backup will be made and recovered objects will be in new database. Name of objects not recovered will be in a "Recovery Error" table. 

    Already occured 5 times in this week, there was no issue with the database for last 9 years. I am in Healthcare, and all updates are controlled by IT. There are 5-7 users at the same time on same server. Windows : 10  (1803). Database is in mdb format. Access : 2016

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-07-01T17:25:36+00:00

    Been dealing with this Access 365 (aka Access 2016) issue since Nov 2019. Continued database corruption issues. MS doesn't seem to give a flip about this well-known issue after over 2 years. Terribly frustrating.

    While I know this has been identified as a "Windows 10" upgrade issue, there are a couple developers here doing fine rolling back their Access 2016 db's to Access 2013, which is what I'm going to do. If any further database corruptions after this rollback, I will convert my backend database to SQL Server.

    Was this answer helpful?

    0 comments
  3. Tom van Stiphout 40,216 Reputation points MVP Volunteer Moderator
    2020-06-18T03:59:33+00:00

    Try it, and let us know how you fare.

    You are part of this community, and this is your way to contribute to it.

    Btw, that version is out of support: 

    https://support.microsoft.com/en-us/help/4456235/end-of-support-for-windows-server-2008-and-windows-server-2008-r2

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2020-06-17T20:14:44+00:00

    Hi to all.

    Does any one tested the BE ACCDB to be on an Ubuntu machine ?

    Since that there is no need for an SQL (by the way we can have SQL on Ubuntu) then the Server 12 R2 is the "mother" of the issues.

    I have many installations :

    Sample 1 --> WorkGroup environment with a shared drive of one client (3-5 users). No problem at all. NO LOCAL TABLES use.

    Sample 2 --> WokGroup with the BE accdb on Ubuntu 18.09 system. No Problem at all. NO LOCAL TABLES use

    Sample 3 --> Server 12 R2. The hell it self with NO LOCAL TABLES. If LOCAL TABLES are on then it's ok (not tested hard yest).

    Conclusion --> ALWAYS SAVE LOCALLY and then with : Currentdb.Execute "Insert Into MainTable Select * from LocalTable", dbfailonerror

    One way or another the Win 10 Pro is a mess.

    Microsoft is a mess too.

    Nonprofessionals with out giving attention to million users/developers of Access.

    I working on to leave from Microsoft and to move in a web app status with MySQL. This is the final solution. A business environment full of Linux Clients & Servers with out MS critical systems at all.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-06-17T15:11:44+00:00

    Is the disable leasing workaround valid for a Server2008R2 Backend?

    only seen reference to server 2012/16

    Was this answer helpful?

    0 comments