SOLVED

DB Corruption

%3CLINGO-SUB%20id%3D%22lingo-sub-2080345%22%20slang%3D%22en-US%22%3EDB%20Corruption%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2080345%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20an%20Access%202013%20DB%20with%20about%2015%20concurrent%20network%20users.%26nbsp%3B%20Each%20user%20has%20a%20copy%20of%20the%20front%20end%20but%20we%20experience%20periodic%20backend%20DB%20corruption.%26nbsp%3B%20There%20is%20no%20discernable%20pattern%20but%20it%20often%20happens%202-6%20times%20a%20week.%26nbsp%3B%20I%20do%20use%20some%20form%20timers%20but%20have%20shut%20down%20the%20one%20in%20the%20main%20menu%20but%20the%20corruption%20still%20occurs.%26nbsp%3B%20%26nbsp%3B%20Has%20anyone%20experi%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2080345%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2013%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAccess%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Visitor

I have an Access 2013 DB with about 15 concurrent network users.  Each user has a copy of the front end but we experience periodic backend DB corruption.  There is no discernable pattern but it often happens 2-6 times a week.  I do use some form timers but have shut down the one in the main menu but the corruption still occurs.    Has anyone experi

1 Reply
best response confirmed by RayValenti (Visitor)
Solution
If any of your users are running Windows 10, then this is most probably caused by a week known bug. Refer to https://www.devhut.net/2018/06/13/access-bug-database-is-in-an-unrecognized-format/ for all the details.