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: Newest
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
    2020-03-30T17:53:47+00:00

    Completed the list; which includes 31 delete queries, 65 append, and 53 update.  These are just those executed during the "morning update" procedure in our database.

    These affect both frontend and backend tables.

    I would think that the queries affecting only frontend tables would not produce any issues regarding the Microsoft error.  Just those affecting backend tables and of course when multiple users are logged in.

    So, once I get back to a facility where I can test this, should be able to dig deeper.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-03-30T17:13:26+00:00

    Wow!  Thanks for the detailed answer.  I'm going to study this and check my app for any of those conditions.  I did modify all the update queries after the query error fiasco but this is a different scenario.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-03-30T16:04:52+00:00

    I began outlining the list of every query and its type from these procedures and macros in their order to further study this conundrum.  There are dozens, so hopefully over the next several days I can work thru this and test to see if any other patterns can be discerned.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-03-30T15:38:20+00:00

    The queries were delete or update queries to tables in the backend that would generate the error.

    But the issue appeared to be when a certain threshold or number of such queries in succession was executed. Using DoEvents or other delay procedures did not make any difference.

    1. The initial test where the one to initiate the queries was not the first user in, the error would always hit on the same query.
    2. If that query was skipped the next query would cause the error.
    3. The group was than divided into three separate groups. 

      Any one group by itself would work fine.  But any two would produce the error.

    Other notes:  (Some of these were noted in a previous post)

    1. If the user was the first one in and others were logged in, the set of queries/macros would work fine.
    2. If another user was logging in while the queries/macros were running, it would produce the error.
    3. If the LBDviewer was used to see the users, the advantage of being the first user in seemed to be lost; ie if they initiated the queries/macros after the LBDviewer was used, it would produce the error.

    All these scenarios could be reproduced over and over.

    Was this answer helpful?

    0 comments