Microsoft Access Database App Error 3046

Julian-Cooper-KPP There was a significant change to address some of the issues around the errors with corrupt/inconsistent databases, which was being rolled out to production, but we have turned back off, and it is possible that this change could cause the 3128/3046 errors.  That change has been turned off via configuration so if users are still seeing this issue after restarting Access, then there must be some other cause.  As many posters have pointed out, this may legitimately be a case where there is locking contention (multiple users trying to modify the same data at the same time), so it may just be an application error or appropriate behavior, it is hard to say without access to the application reporting the error. We do not have evidence that this is an issue being experienced broadly.