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-21T06:02:05+00:00

    JD,

    Do you have the fe db as .accdb, and the be db as .mdb ? Does that work ? How long ago did you do that, and how is it holding up with this "working from home" situation ?

    Interesting on DoCmd.RunSQL vs DoCmd.OpenQuery. I'll look into it.

    Thanks

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-04-21T06:09:43+00:00

    Sorry, one additional question (I'll shut up after this) - A couple users have told me that they are losing data after a data corruption and compact & repair. I thought that wasn't suppose to occur with a compact & repair ?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-04-21T13:55:02+00:00

    Hi George,

    Yes, MDB back-ends and ACCDB/ACCDE front-ends will work together. The opposite (ACCDB back-end and MDB/MDE front-end) does not work.

    I used to have multiple Applications, some with an MDB back-end, some with an ACCDB back-end. I had corruption issues for a whole year, after moving from W7 to W10. Then, I realised that only the ACCDB back-ends were getting corrupt.

    Since I made the change to MDB back-ends, 2 months ago, I've had no corruptions at all. Working from home via VPN did not change anything to that.

    Replacing DoCmd.RunSQL with DoCmd.OpenQuery did reduce the occurrence of the problem, but did not fully solve it.

    It could also be that something on the server side (shared-folders containing back-ends) was changed on the IT side, without my knowledge. But I'd say that the MDB trick is worth a try.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-04-21T14:06:52+00:00

    My experience was as follow:

    General corruption: can go both way, but usually without record loss.

    "windows 10 corruption issue" discussed in this thread:

    • If the database is closed and repaired right after the corruption occurs, then I usually don't loose any data.

    -If users keep capturing data after the corruption has occurred (after the first error message occurs), then these records are usually lost, will look like #### in the back-end.

    Via VBA, I force the application to close and put it under maintenance (keep users out) whenever the error 3343 or 3049 occur.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-04-21T14:19:12+00:00

    Don't forget that corruption can also exist outside of the current bug and such corruption can lead to data loss.  Corruption is unpredictable.  I've seen entire databases corrupted beyond any recovery.  This is why backups are critical!

    Running any Access database over VPN is asking for trouble and corruption.  Access is ONLY meant to be run over a LAN.  Everything else is a risk, VPN is one of the highest risks for encuring corruption just by its nature.

    You should always make a backup prior to compacting.

    Was this answer helpful?

    0 comments