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-01-30T17:09:39+00:00

    I'm new to this thread.

    I'm relieved and not at the same time after reading these 33 pages.

    I'm a small-time developer with 500 user sites,

    Setup is : Access 97 on a shared drive on a Windows server

    and PCs with  VB6 program installed accessing the database.

    All going well for 25 years until past 6 weeks when all the clients had to get their PCs updated to Windows 10. 

    I now have email phobia!

    Just waiting for the next email to announce the dreaded  3343 database corrupt message.

    Has anyone had persistent positive feedback on the simple option of  changing the folder of the database file on the server? 

    from Daniel Pineault's site:

    https://www.devhut.net/2018/06/13/access-bug-database-is-in-an-unrecognized-format/

    MAKE A NEW FOLDER: As astonishing as this may sound, several users have now confirmed that simply creating a new folder (on the same drive) and moving their database to the new folder resolved the issue.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-01-30T14:01:19+00:00

    Has anyone developed a Bat file that removes the Disable_Leasing registry keys from the Server (runned with admin priveleges) ?

    I wouldn't like to ask the ITs to remove manually these registry entries. I tried a lot to convince them run a single batch file with the disable leasing. Now asking them to remove manualy registry entries will be ... world war 3 !!!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-01-29T03:22:33+00:00

    Thanks for the clarification David.  Yes I agree that in large organisations that the IT dept has control over what patches can be applied to both clients and servers but in most cases if they are not willing to apply a client side fix that has little or no side effects, they will not be willing to apply any fix to a shared server where there are known side effects.

    I just think it should be made clear in this thread that the Client side fix does in fact work when applied to all Win 10 clients and getting IT depts to apply it is much easier than getting them to apply any server side "fix".

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-01-28T20:16:38+00:00

    I believe this all surfaced with Windows 10 update KB4100403.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-01-28T20:00:45+00:00

    So with each update, you have to reapply the registry fix after the update and hope it'll still work ?

    Does anyone have an idea which Windows 10 builds are affected by this issue?

    As I recall, this issue started with a specific update.

    Only a few of our Windows 10 machines ever experienced this problem and after applying the fix to only those machines the problem has largely disappeared.

    Was this answer helpful?

    0 comments