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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-01-27T13:15:58+00:00

    Two of my clients have used a NAS for back ends (long before the issue discussed here) and both were troublesome, so I would not personally go down that route except as last resort (but I assume it is a guaranteed solution to this issue). If necessary I would try Mark's method or stick the back end on a spare Windows PC and disable leasing on that. I have no idea how the performance on a fast dedicated PC would compare to that of a decent NAS though, in this context. Your issue seems to be with performance, so I suspect you will have to test the various options.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-01-27T12:28:01+00:00

    What If the backend access db is installed on a NAS Disk ?

    Any experiences on that ?

    I would prefer to buy to my customers a NAS Disk and install backends there, in order to get rid of this mess that MS gave to us and save my company from further problems ...

    Any experiences regarding this ?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-01-27T11:57:35+00:00

    Thanks for the answer..

    Of course I will try it.

    If anyone else is experiecing performance issues, please share with us.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-01-27T10:49:47+00:00

    Hi Theodorus (and others still struggling with this),

    I cannot exactly answer your question, but I'm puzzled why you and others have apparently not tried the variation detailed by Mark Mauger on November 29th (the last post on this date, on page 26 for me). It sounds fairly simple to test, but no-one has reported back as yet. Maybe it will not suffer the same performance issue?

    Luckily my clients have eventually been able to disable leasing on their servers and have not reported any performance issues as yet.

    Good luck!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-01-27T04:16:43+00:00

    Sorry for asking but I am still a bit confused. 

    Up to now we have:

    1. The SMB cache solution that can be applied on client machines and resolve the issue

    Or

    1. Apply the disable leasing fix on the server, without applying the SMB cache solution on each client pc

    So I kindly ask you to tell me your experiences with performance of each solution. I experience with Disabling Server leasing solution, serious lack of speed when executing action queries and dlookups from windows 10 clients. With windows 7 clients there is also lack of speed but less important. Is the solution (1) that is applied on each client machine faster? Are you experiencing same speed problems?

    Please MS don't abandon us..

    Was this answer helpful?

    0 comments