I completely ignored the Access 2013 Runtime installs, as I did not realize the security update had just been pushed out in my client's environment.
I mistakenly assumed that it must have originated with one of the handful of users with a Click-to-Run (C2R) version of Access. I recognized the error message immediately, but it took me quite awhile to identify the source of the error. After this update is installed, Microsoft Access databases that are stored on a network share can't be accessed by multiple users simultaneously. In this specific situation, the sudden outbreak of the bug at our client could be traced to a manual rollout of the Office 2013 Security Update, KB5002104. The Patch that Broke the Access 2013 Runtime However, that changed yesterday when I got an email, a voicemail, and many, many automated bug reports announcing the arrival of the 2021 Holiday Bug. Whenever a user with an affected copy of Access connects to a backend database, then any other user that attempts to connect to the same database receives the error, "File already in use." Until recently, I had managed to avoid this error as most of our clients use the Access 2013 Runtime to run our applications. As I've already written about, a December "Patch Tuesday" security update from Microsoft introduced a bug that affects shared Access database files.
0 kommentar(er)
