Count current database connections? 1

[bradles]

Hi all - have a complex app throwing error 3048 (too many databases) and I'm looking to count the database connections but haven't been able to find a way. The connections to count include all form controls (combos, listboxes and forms) and I seem to remember a long distant thread somewhere but can't locate it.

Architecture is a split front/backend database with 15 tables, some use of pivotcharts for dashboards (2010 Access version), heavy use of ListViews to load and close recordsets, and 3048 thrown with a form that's opened in a multiple instance scenario.

So - how to count current connections back to the backend?

Brad Stevens

 

[dhookom]

I would try to limit the number of controls with Row Sources particularly in reports.

Duane
Minnesota
Hook'D on Access
MS Access MVP 2001-2016

 

[bradles]

Thanks Duane - totally agree and I've got quite a few directions to go, but I want to measure the impact of changes by measuring the connection count.

Any ideas there?

Brad Stevens

 

[dhookom]

No idea on how to determine the connection count. I have been paying attention to Access groups for 20+ years and haven't seen any way to determine the number of connections.

Duane
Minnesota
Hook'D on Access
MS Access MVP 2001-2016

 

[bradles]

Yep, pretty confident you'd know how if it existed Duane!
Thanks for your input.

Brad Stevens

 

[MajP]

This is normally a complexity issue. Culprit is often multiple subforms, because you can quickly multiply the connections. It could also be a loop creating multiple module level recordsets not going out of scope. My understanding is 2048 connections.
1) Compartmentalize your design. I see too many bad databases where people want to do everything from a single form; search, add, modify all on the same form. Nothing worse then nested subforms IMO. Normally my search forms are seperate from my edit forms and same with add.
2)If you have lots of tabbed or hidden subforms, consider a single subform control where you load the source object when you tab or make visible.
3) If you have rarely used controls like combos/listboxes then load them only on entry