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-02-24T17:09:29+00:00

    Hear Hear

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-02-24T17:28:13+00:00

    Why does MS drop support and kill off established db products like Access and FoxPro which have large user communities ? These decisions just further encourage developers/users to pursue non-MS solutions.

    Was this answer helpful?

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

  4. Anonymous
    2020-02-25T02:11:32+00:00

    Make sure the the 'reconnect' option box is unticked if you use the GPO drive map option. That will definitely fix it, did for me.

    Hello Tomas. 

    Thanks dor the reply. 

    What do you mean by saying reconnect option box with GPO. Where can we find this.

    I am also condirming the following:

    1. If we are using the server disable leasing option, everything seems fixed. If this option is selected then corruption returns (but not so often) through mapped networked drive and corruption is not appearing again when using unc path for linking to the back end. 
    2. The other solution, the SMB registry fix, that is applied only on client machines, has a tremendous impact on speed, especially when using dlookups or dsums. The server disable leasing solution is also having a speed impact but is by far faster than SMB registry fix. 
    3. Tried the erd solution that mentioned here. The "turn off background refresh of group policy". So I dissabled all other solutions, made a clean restart to serveer and client machines, apllied this to server, rebooting again everything and checked. Didnt worked for me, so I am asking Thomas to help with the "unticked" reconnected option box with GPO which I do not understand, so I will try again

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-02-25T03:20:30+00:00

    Hi,

    Do you use group policy to map your network drives? If so make sure the 'Reconnect' option is unticked for each mapped drive. See attached.

    This fixed the problem for me instantly.

    Hope this helps

    Tom

    Was this answer helpful?

    0 comments