This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(288, 39%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
The last step in my Access application (before DoCmd.Quit) is to close the connection to the backend database on the network drive, as follows:
This has always worked until one of the workstations was upgraded to Windows 11. Now when that workstation exits out of the Access app, the backend database remains locked. When I list the open connections, the front-end database shows up 3 times and the backend database 6 times (see screenshot)! Any idea how I can force these to close?
Did you check if db.Close fails and gives some error messages?
Yes, I added the error check and there was no failure...
Hi,
The build 17928.20156 with the bugfix is now available for the current channel. You may have to select "Update now" in File - Account to get it immediately. Details can be found in our documenting article on AFo.
Servus
Karl
Access Forever News DevCon
Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg
Installing the update did the trick. Many thanks, Karl.
Just curious if you know why the build number updated to 20156 in Account but still shows 20114 in About Access?
Hi,
Just curious if you know why the build number updated to 20156 in Account but still shows 20114 in About Access?
That's an old problem: The build number in the About Access screen is rubbish, i.e. from a random dll, which doesn't get updated with every new Office build. Only the Office build number directly in the Account page is meaningful and tells the current status correctly.
Servus
Karl
Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg
Hi,
You didn't mention your version and build number of Office. So, I can only guess that you are most probably one of the many victims of a current Office/VBA bug. You can find details and the information about the planned fix in our documenting AFo article.
Servus
Karl
Access Forever News DevCon
Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg
Installing the update did the trick. Many thanks, Karl.
Just curious if you know why the build number updated to 20156 in Account but still shows 20114 in About Access?