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-04-02T00:42:50+00:00

    Hi George  - this problem is limited to Windows10 clients accessing central data over a LAN. There were no reports of any problems on sites using mixed versions of Access front ends over the years. This Client side registry fix, applied to ALL win10 clients, will fix the problem, ie the constant corruption where the databases go into unrecognised state and worse. It is purely a LAN problem  where Access on Win10  frontends accesses any .mdb or .accdb databases over a LAN. The problem has nothing to do with Access, it is just that Access databases are like canaries in the coal mine, the first to show problems, being extremely sensitive to any network disturbances. The issue introduced by Windows10 2 years ago has been constant. I think this is why the Access team can do nothing to effect a solution - it is the operating system that is causing the problem, and they have no control over it. There are too many other factors for the O/S dev team to consider, such as cloud compatibility and capabilities, for them to undo the changes that are causing this problem in Access over LANs. Microsoft want to make windows 10 the de facto o/s for accessing Cloud Services. The effect on Access is tiny collateral damage that they can't fix without causing other problems. Especially when there is a "FIX".

    My advice: Implement the simple Client side Registry fix. It works. It will make your life easier.

    Hope this helps you make a decision.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-04-01T21:38:04+00:00

    Hi WayneAprato1!

    That is correct!  I have one client that provides the application on a server using remote desktop connections and they have not had this issue.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-04-01T20:51:47+00:00

    I've been following this for a long time and from my understanding of the issue so far the problem occurs when there is a network connection between FE and BE.

    Is it fair to say that this corruption issue does not occur where users are accessing the database via remote desktop where both BE and FE are on the same server drive?

    Could someone please clarify that point for me?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-04-01T18:55:38+00:00

    Yes, this is an almost 2 year old bug.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-04-01T18:34:57+00:00

    So, based upon the link, this is not a new update, but the one first introduced in the Spring of 2019, correct?

    Was this answer helpful?

    0 comments