"Cannot open any more databases" (error 3048) issue persists. Possible workaround/suggestion.

Question

1. So the version number of Access is not relevant to a user getting the error or not.
2. Nor is it affected by Trusted Locations.
3. However, it does seem to be isolated to the DAO library.

I write add-ins for folks in my organization. All of us are updated to the latest Office version ( which is why I concluded #1 above ... it happens to some, not to most).

I discovered the Trusted Locations solution and wrote an entire module of additional code to add both the user folders and the server database locations & their subfolders to Trusted Locations but it didn't solve the issue (#2 conclusion)

But when I included both ADO and DAO modules (one to fall back to on failure of the other, with exit user messages to report what (if anything) worked and what didn't), the affected users all reported a failure only with DAO code. The ADO worked as expected.

Hopefully this will help someone tearing out their hair as I have been for days on end. And perhaps even inspire an actual ... dare I say ... "fix?"

Answer 1

Just today I deployed this really nice utility by isladogs: https://www.isladogs.co.uk/available-connections/index.html

to monitor the situation.

My app is already limiting db connections (e.g. I fill most comboboxes with static data, and I only load subform tabs that are being visited) but some users still get this error.

The actual fix has to come from MSFT. Use the Frownie in the ribbon to express your dissatisfaction, and have the users do that too. Put it in business terms that MSFT can understand. I am told they actually take note of these frownies.