Getting error message Can't open any more databases

[CD Tom]

Just lately some users of my application have been getting the message (Can't open any more databases. When I look at their task manager, I see Access running in the Apps section and when I look in the background section I find that access is running 4 or 5 times. My users are running Access Runtime version 13 32bit. On my machine I don't get the message but if I look in my task manager, I see Access in the Apps section and I see it once in the Background section. If I close my application it is gone from the Apps section, but it is still in the background section.
Does anyone know what the heck is going on???
Thanks for any help.

[jimatqsi]

Could you offer some more details on this? Under what circumstances does this happen? Immediately upon entering the app, or after some period of time? Does your app explicitly open other database apps? If so, can you add some logging to that process so that you might have a record of events?

Task manager can tell you more. If you explore the view a bit it will tell you the name of the Access database that is running. Is it the same app multiple times?

I think adding some event logging is your first best action.

[CD Tom]

Ok thanks for answering. When the app it started everything is ok, when the user say goes into the edit members section of the app it works fine for the first couple of times, but after maybe three of four time they will then get the error message, when I look in the task manager I see that access is running multiple time in the background section. I kind of looks like the app opens up each time the user does anything three or four times.

[jimatqsi]

Does your app explicitly open any database apps? I'm thinking something along the lines of

Dim ctl As Control
Dim db As DAO.Database
Dim Path As String

Path = "C:\test\"

appMasUtil.OpenCurrentDatabase Path & (databasename], True

[alizaheer240]

It sounds like the issue you're encountering might be related to how Microsoft Access handles multiple instances and background processes, particularly with the Runtime version. There are a few potential causes and solutions to consider:

1. Multiple Database Connections: The message "Can't open any more databases" suggests that the users might be hitting a limit on the number of open database connections. Access has a limit on the number of objects (tables, forms, reports, etc.) that can be open at the same time. You might want to check if your application is opening multiple database objects without properly closing them. Review the code and ensure that all recordsets, forms, and other objects are properly closed and set to Nothing when they're no longer needed.
2. Background Processes: Seeing multiple instances of Access in the task manager, especially in the background section, might indicate that Access isn't fully closing when the application exits. This could be due to lingering processes or orphaned database connections. Here are a few things to check:
   • Check for Unclosed Objects: As mentioned earlier, ensure that all Access objects (recordsets, forms, reports, etc.) are explicitly closed in the code before the application exits.
   • Ensure Application Closes Correctly: Ensure that the application is programmed to fully quit and release any resources. Sometimes, Access Runtime can leave background processes running if something isn’t fully terminated.
3. Version Mismatch or Compatibility: Since you're using Access Runtime version 13 (which corresponds to Office 2010), it’s worth checking if there’s any version mismatch between your development machine and the users' machines, or if there are any compatibility issues. Sometimes, different versions of Access or even running 32-bit Access on 64-bit systems can cause strange behavior.
4. Corrupted Runtime Installation: It's also possible that the Access Runtime installation on the affected machines has become corrupted. Reinstalling the Access Runtime or updating it to a newer version might resolve the issue.
5. Database Size or Corruption: If the database being used by your application has grown large or is corrupted, it could lead to issues with opening multiple instances or reaching the database connection limit. Consider compacting and repairing the database to ensure it's functioning optimally.

Suggested Troubleshooting Steps:

• Review Code: Ensure all objects are properly closed and set to Nothing in your code.
• Task Manager: Monitor the task manager to see if Access is closing completely or if it's getting stuck as a background process after closing.
• Check for Updates: Make sure both your Access Runtime version and any updates for it are installed.
• Reinstall Access Runtime: Try reinstalling the Access Runtime on the affected machines.
• Compact and Repair Database: Regularly compact and repair the database to avoid any potential corruption or excessive size issues.

By addressing these areas, you should be able to identify the cause of the multiple Access instances and the "Can't open any more databases" error. Let me know if you need further clarification!