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: Oldest
Most helpful Newest Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. Anonymous
    2019-11-27T19:28:58+00:00

    Hi Wayne,

    The biggest problem with this issue is that we still don't have a way to reproduce the problem in a controlled environment.

    Nobody has been able to give us a situation where it is "Do these steps", then "Database is corrupted".

    We believe we understand the change in Windows that caused the increase in corrupted databases, and have been testing changes that we hope will alleviate the problem in production.  Initially, that will be for O365 Monthly Channel users.  It will not necessarily address all the issues, particularly in environments with users using different versions (if someone using Access 2016 corrupts the database, it may still be reported as corrupt when it is opened in Access365).

    I am not suggesting this as a workaround, because I know it isn't a trivial transformation, but if this is causing you significant issues, it is worth considering using Access for the front end, and storing data in  SQL Server.

    We will share more information when we have it, but I don't want to make promises we can't deliver on.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-11-27T19:38:46+00:00

    Thanks Shane. I am not experiencing problems at the moment and have not seen issues for many months.....touch wood.

    One client that was experiencing continual corruption several months ago is no longer experiencing problems since the DisableLeasing fix was applied to the server. They are running Office 365.

    Another newer client, also running Office 365, has not been experiencing any issues either. The DisableLeasing fix was applied to the server prior to the installation of their databases.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2019-11-27T19:42:03+00:00

    I don't think the DisableLeasing fix is being referred to in that post as not working.

    The way I read it is that other fixes that have been trialed since have not delivered the desired outcome.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-11-27T20:21:20+00:00

    Sorry but we have paid for MS Access, we have developed everything in MS Acces and we want to continue using this product, that used to be a revolution when it was commercialy deployed and now it is a deatroyed by the company that has created it. 

    I am a pro developer in MS Access environment for about 15 years. And we all know that we were satisfied up to the version of 2003. This is why most of the devs are still using it. Was faster, more dev friendly environment and even more reliable. 

    Now we experience bugs and corruption, because we did something wrong. And it is wrong to still stay with MS, that is not supporting our business and our customers. 

    It has been 1.5 years with this bug. If you cannot reproduce the error, then for God's sake make a phone call or send an email to a couple of these people here in this thread that are having the problem. Get out of the cage and give solutions to people around that still believe in you. 

    And please develop access again. I feel that you believe it is somehow an"internal competitor" to other products of ms. So my opinion is that you are doing this on purpose. 

    My suggestion to all you around that you are hitted by this kind od MS practices. Instead of moving forward to another ms product for resolving the issue, I suggest to move away from MS. The time that you will need for migrating to another ms product, would be wiser to spend it to other sophisticated products that are out there. 

    PS: Why there arent such bugs in SQL server? Because they pay more attention to that kimd of product and left access to suffer...

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments