Too many connections

A couple weeks back I posted a problem with selects from combo boxes
causing additional logons with a SQL Sever backend. (And thanks to those
who responded.) However, upon further research we discvered it's actually
subforms causing the problem. We're using windows authentication and the
Native Client driver.

Example: A form loads that has three subforms on it, causes three
additional logons.

Any ideas?

A couple of questions:

1. Are you using linked tables for the combo boxes rowsources? Is there any
"ADO connection code going on here?"

2. What operating system are you on?


--
Bob Larson

Free Tutorials and Samples at http://www.btabdevelopment.com

__________________________________


"Rick" wrote:

A couple weeks back I posted a problem with selects from combo boxes
causing additional logons with a SQL Sever backend. (And thanks to those
who responded.) However, upon further research we discvered it's actually
subforms causing the problem. We're using windows authentication and the
Native Client driver.

Example: A form loads that has three subforms on it, causes three
additional logons.

Any ideas?

=?Utf-8?B?Ym9ibGFyc29u?= wrote in
:

A couple of questions:

1. Are you using linked tables for the combo boxes rowsources? Is
there any "ADO connection code going on here?"

2. What operating system are you on?



Yes, on both accounts, at least in some subforms there are ADO connections
and all the tables are linked (since it's a SQL server backend.) I should
mention that this main form is never closed, but hidden when ever it loses
focus.

The users are either on XP (about two thirds) or win2k. It seems to with
all of them. (We needed to install MDAC with the win2k machines).

Have you tried setting ONE global ADO connection object when you open your
database and then referring to only that when needing anything from the
server (including the rowsources for the combos)?
--
Bob Larson

Free Tutorials and Samples at http://www.btabdevelopment.com

__________________________________


"Rick" wrote:

=?Utf-8?B?Ym9ibGFyc29u?= wrote in
:

A couple of questions:

1. Are you using linked tables for the combo boxes rowsources? Is
there any "ADO connection code going on here?"

2. What operating system are you on?



Yes, on both accounts, at least in some subforms there are ADO connections
and all the tables are linked (since it's a SQL server backend.) I should
mention that this main form is never closed, but hidden when ever it loses
focus.

The users are either on XP (about two thirds) or win2k. It seems to with
all of them. (We needed to install MDAC with the win2k machines).

=?Utf-8?B?Ym9ibGFyc29u?= wrote in
:

Have you tried setting ONE global ADO connection object when you open
your database and then referring to only that when needing anything
from the server (including the rowsources for the combos)?

I thought about that as I was typing the last note. I'll check inot that. I
think it usuall uses the currentdb.connection (Access 97), but I'll se if
there's other rogue connections. Thanks!

=?Utf-8?B?Ym9ibGFyc29u?= wrote in
:

Have you tried setting ONE global ADO connection object when you open
your database and then referring to only that when needing anything
from the server (including the rowsources for the combos)?

A followup: I could not find any extraneous connections. It IS using a
global connect object. How would I specify connection for the comboboxes?
Would I need to set a recordset as rowsource? (I know I can't do that with
Access 97.)