Combobox cause a new connection

[Rick]

Recently, we converted an Access back-end to SQL server and discoverd
hundreds of connectons per hour for about 25 people using it. Finally, we
figured out that very combo box with a table query as rowsource created a
new login every time the form is loaded. We're using windows authentication,
so no user/password is required...fortunately!

Is there any way around this?

 

[ruralguy via AccessMonster.com]

You could leave the ComboBox RowSource empty and set it in the Enter or
GotFocus event of the ComboBox control.

 

[Rick]

You could leave the ComboBox RowSource empty and set it in the Enter
or GotFocus event of the ComboBox control.

That's a thought. Thanks!

 

[Rick]

You could leave the ComboBox RowSource empty and set it in the Enter
or GotFocus event of the ComboBox control.

Well, it didn't solve the problem. There has to be something at database
level, either front end or back. Anybody know?

 

[ruralguy via AccessMonster.com]

Are you still convinced it is the ComboBoxes that are causing the problem?

You could leave the ComboBox RowSource empty and set it in the Enter
or GotFocus event of the ComboBox control.

[quoted text clipped - 6 lines]
Well, it didn't solve the problem. There has to be something at database
level, either front end or back. Anybody know?

 

[Rick]

Are you still convinced it is the ComboBoxes that are causing the
problem?

You could leave the ComboBox RowSource empty and set it in the Enter
or GotFocus event of the ComboBox control.

[quoted text clipped - 6 lines]

Is there any way around this?

Well, it didn't solve the problem. There has to be something at
database level, either front end or back. Anybody know?

Yes, ween the combo boxes are removed, there's only one login.

 

[ruralguy via AccessMonster.com]

Have you tried using a persistant connection?
http://www.granite.ab.ca/access/performancefaq.htm

Are you still convinced it is the ComboBoxes that are causing the
problem?

[quoted text clipped - 7 lines]
Yes, ween the combo boxes are removed, there's only one login.

 

[Rick]

Have you tried using a persistant connection?
http://www.granite.ab.ca/access/performancefaq.htm

Are you still convinced it is the ComboBoxes that are causing the
problem?

[quoted text clipped - 7 lines]

Well, it didn't solve the problem. There has to be something at
database level, either front end or back. Anybody know?

Yes, ween the combo boxes are removed, there's only one login.

I suppose it's worth a shot, but the main form of this app is open all the
time. We just hide it when other forms are called. I'm presuming the bound
recordset is open whenever the form is.

 

[ruralguy via AccessMonster.com]

I would have to say yes, you are already keeping a persistant connection.
Going back to the ComboBoxes, you were getting repeated connections event
when *all* of the RowSources were blank until you entered them with the
cursor?

Have you tried using a persistant connection?
http://www.granite.ab.ca/access/performancefaq.htm

[quoted text clipped - 6 lines]
I suppose it's worth a shot, but the main form of this app is open all the
time. We just hide it when other forms are called. I'm presuming the bound
recordset is open whenever the form is.

 

[Rick Brandt]

That's a thought. Thanks!

What "real" problems are the connections causing? Would you have even known
about them had you not looked for them?

I have the same setup with a few hundred users and it has never been a
problem.