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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-06-12T07:00:50+00:00

    Hi Shane and Daniel,

    I have asked my clients to try this. We have VB6 frontend application which is installed on workstations and it connects to the database(MS access) which on server(Win 7).  5 workstations are of different window version (Win7 and windows 10). This setup was working fine since last 10 years. Suddenly after update its causing issue.

    Thanks,

    Amit Borse

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-06-11T18:19:12+00:00

    Shane Groff,

    I have a Client that is now reporting this error on the only machine that has Windows 10 64 bit.  All other machines are on Windows 7 64 bit and reporting no issues.  I have sent the work-arounds to their IT department and am waiting to hear back.

    Has the issue been identified?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-06-11T17:53:35+00:00

    Hi Amit,

    Just to clarify, you have an Access front end database, and an Access back end database, with the back end database stored on a network share, is that correct?

    If so, which version of Windows is in use for the machine running the front end (client), and which version of Windows is in use on the machine hosting the back end (server)?

    You can certainly set the registry key mentioned in that article (you should do it on both client and server machines), although I'm not certain if it will impact Windows 7, but if you try it, let me know whether or not it helps.

    The other possible source of this issue is a May update to Windows 10 ( KB 4100403), if either client or server is on Windows 10, you can try the workaround described there, which is to ensure that SMBv2 or SMBv3 is enabled as described here KB2696547 .

    Shane

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-06-11T17:49:15+00:00

    I'd trying implementing the fix, even on Win7.  Please report back either way.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-06-11T17:45:47+00:00

    Hi Shane and Daniel,

    Thanks for looking into this. The link you shared is for windows server 2012. The client who is getting this issue is on windows 7.  Any suggestion here?

    Thanks,

    Amit Borse

    Was this answer helpful?

    0 comments