How do I close orphan database connections?

DarrellDoesData 20 Reputation points
2024-09-08T16:49:41.33+00:00

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:
User's image

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?

User's image

Microsoft 365 and Office | Access | Development
Microsoft 365 and Office | Install, redeem, activate | For business | Windows
Microsoft 365 and Office | Access | For business | Windows
{count} votes

Accepted answer
  1. Karl Donaubauer 2,061 Reputation points MVP
    2024-09-10T15:43:22.42+00:00

    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

    1 person found this answer helpful.

3 additional answers

Sort by: Most helpful
  1. Karl Donaubauer 2,061 Reputation points MVP
    2024-09-11T16:26:08.5533333+00:00

    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 Forever News DevCon

    Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg

    1 person found this answer helpful.

  2. Karl Donaubauer 2,061 Reputation points MVP
    2024-09-09T08:34:14.3266667+00:00

    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


  3. DarrellDoesData 20 Reputation points
    2024-09-11T16:16:17.2066667+00:00

    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?

    User's image

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.