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. Anonymous
    2020-04-22T15:22:00+00:00

    George,

    Of course you can always change the registry again to delete keys and change values. I guess technically you would have to capture the values of those keys before the change in order to be able to restore them to what they were before they change. I am not doing this and is beyond the scope of what I can advise you on. Yes, you have to make the registry change on every Windows 10 client that uses the database. It only takes one PC to corrupt the database. Whether or not you need admin privileges and whether you will be prompted for a password is also beyond what I can advise you on. The user definitely needs permissions to add/update those registry keys, so running as administrator is the safest way to assure that. You will probably will want to consult with your IT people and do some testing to see what you have to do in your environment.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-04-23T18:24:02+00:00

    Hi JD,

    Success !!! Thank you, Thank you !!!

    This is the first time in over a month I didn't see "Database corruption" complaint emails after I logged in. Did a bit of tweeting on the setup & backup processes due to the extension change, but all is well this morning (reference to the "3 Idiots" foreign movie I watched last night. Great movie ! https://en.wikipedia.org/wiki/3_Idiots ).

    I hope this fix keeps working until they discontinue this db. I have the client side registry fix in my back pocket as "Plan B". It's too bad MS hasn't taken more of an interest in this issue after over 2 years. I guess it's up to them if they want to continue to lose customers.

    Take care,

    George

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-04-27T19:44:34+00:00

    Bad news - The switch to .mdb hasn't stopped the data corruption issues. My database has corrupted twice since I implemented the change.

    I am now considering Plan B - The client side registry fix. However, I am curious what exactly this registry fix does if someone could explain.

    Thanks,

    George

    Was this answer helpful?

    0 comments
  4. 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

  5. Anonymous
    2020-04-28T04:16:57+00:00

    Hi Everyone - ie fellow crash victims . .

    On our system we have a main backend DB that was stored in a seperate RAID harddrive box. - It floated between 200meg and 300meg in size and was stable with 20 users.

    After we installed a new server box HP Proliniant ML350, we moved the backend tables to a Raid array inside the server box. It did run faster, but we also started experiencing the corruption issues. 

    most commonly around 8.30 - 9.00 am as staff started logging on. sometimes it would crash several times in 1 day.

    we tried fixing networks points - cables - switches etc - thinking it was some sort of packet crash causing the corruption. . . nothing worked.

    about 6 weeks ago i moved the BE tables back onto the external RAID box - and have not had a crash since . .  

    The big question is WHY . .  mysteries of the universe . . 

    Cheers

    PaulG

    Was this answer helpful?

    0 comments