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 No comments

604 answers

Sort by: Most helpful
  1. Anonymous
    2021-01-22T18:21:10+00:00

    I agree that migrating to SQL Server would be the best option. However, if the company does not want to commit to that conversion & as in my case, they are moving to a more proprietary, custom built system, their intent is keeping their Access database(s) running until a full migration to a new system can be completed.

    I haven't heard that the performance with a SharePoint backend is awful. In fact, I heard the opposite from db analysts here who made the migration to SharePoint. In fact, I will be having a meeting with them later today to get all our questions answered.

    Yes, moving on to another client/company is an option but given the recent pandemic, Federal administration transitions, and increasing unemployment, I'd rather stay put until resolutions regarding our national/international issues are more clear.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2021-01-15T10:11:53+00:00

    Hi Mark,

    We are not driving people away from Access on purpose, and do understand the pain this problem has caused.

    We won't give up, and will update status here when we can: https://support.microsoft.com/en-us/office/access-reports-that-databases-are-in-an-inconsistent-state-%EF%BB%BF-7ec975da-f7a9-4414-a306-d3a7c422dc1d

    Shane Groff

    Access Engineering

    Hi Shane,

    It has been 6 months since the last update. Please will you post another update when you get a chance?

    Thankfully the official work around still seems to be working for the clients who have been affected, but their IT departments would like to restore normal server functionality asap. In the meantime, the official page needs to show that it is still being worked on please!

    Many thanks,

    David Nye

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-08-18T17:40:03+00:00

    Any attorneys reading?  Would a class action lawsuit not be possible?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2020-07-15T15:15:46+00:00

    Sir, I am polite to Shane because while Microsoft may be a big company Shane is a human being doing a difficult job.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2020-07-14T20:18:13+00:00

    Thank you Shane.  Perhaps occasionally you could provide any insights you have as to what anyone there knows about it.  We are pretty much in the dark and any light you can shed is greatly appreciated.

    Sorry my friend JAZSchaefer but you are very polite to Shane Groff. We do not expect any highlights or any insights from him/her (I do not know) or from anyone in MS. They are joking with us. We want a stable resolution to this. And this has to be done NOW.

    Microsoft is able to put a devil in a bottle. All these software, RDBMS, .NET, Servers, SQL,, Windows etc. They know exactly what they have done and simply they do not want to resolve it or take back the changes they made with that damn update of Windows 10 that cost us our companies and our lives.

    WHY ?

    Simple:

    Access is able to do the job for the biggest majority of companies with simple desktop apps and with simple networking. And also has a good deployment. It is just ... a file. And they do not like this. This is why they are killing access slowly after 2010. Because access was a simple revolutionary idea that would be always alive and confront with all these SQL Server and .NET apps for desktops ... All these, in most cases for small companies, are like having an expensive Nuclear Aircraft Carrier to go for fishing. Also why to invest on Cloud Dbs since Access is ... cheap and does the job. And since they are not having the guts to make a clean statement: "Access if over for us", they made this on purpose to just take out the biggest advantage. Access ability to work in network environments. So they will keep it alive for a single desktop but dead for companies that require network access of their dbs.

    And you my friend that you are reading this and you believe that I am over reacting, just think about it.

    MICROSOFT is a GIANT and cannot resolve an issue that they have created by their own with an update of windows, after two years.

    And if you are still having second thoughts, then read it again:

    MICROSOFT is a GIANT and cannot resolve an issue that they have created by their own with an update of windows, after two years.

    If there will be no resolution to this, then I believe that we need to think the legislative way to push Microsoft and gain back the money we have lost and our reputation. In EU there are specific rules about issues like this.  I will go forward and inform a Greek Member of the EU Parliament with a link of this thread, since this issue had a huge impact to the viability of our companies as also our customers. I just cannot accept Microsoft doing this. Sorry ...

    PS:

    Please someone try another potential workaround that I have posted just a few post before. It might be a good alternative as it also gives better speed.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments