G
Guest
I just ran into this problem. It seems to be a popular topic judging from
the items posted here and elsewhere. I can't see how my application could be
using 2048 tableIDs (each of which is a separate database connection, I
guess?), but maybe I don't understand what is going on here; so I would like
to post a couple of questions and hopefully get some insightful replies.
1. Does each active query use up a tableID? I usually define a query for
each base table (i.e. tbl A would have qryA, tblB would have qryB, ...) and
then I use the queries, not the base tables, in other query definitions (i.e.
qryAB uses qryA joined over qryB by a common field). Does doing things this
way eat up a bunch of tableIDs?
2. In continuous forms, where the form has a field based on a lookup combo
box, does each record displayed by the form chew up a tableID, or is a single
tableID used for the whole form? In other words:
if this is the form:
datasource is qryA which is based on tblA
form Field1 is bound to Field1 in qryA and the underlying field (in tblA) is
an ID field which has a lookup combo box using qryX (based on tblX) to show
the field value rather than the actual ID number
form Field2 from qryA
and the recordset that the form displays happens to have 30 records
then how many database connects are actually being used? Lots? Any way to
avoid a huge overhead of db connections?
Or is the problem (too many databases open) due to something altogether
different?
Hope this makes sense. Any help will be appreciated --
Chuck Flood
the items posted here and elsewhere. I can't see how my application could be
using 2048 tableIDs (each of which is a separate database connection, I
guess?), but maybe I don't understand what is going on here; so I would like
to post a couple of questions and hopefully get some insightful replies.
1. Does each active query use up a tableID? I usually define a query for
each base table (i.e. tbl A would have qryA, tblB would have qryB, ...) and
then I use the queries, not the base tables, in other query definitions (i.e.
qryAB uses qryA joined over qryB by a common field). Does doing things this
way eat up a bunch of tableIDs?
2. In continuous forms, where the form has a field based on a lookup combo
box, does each record displayed by the form chew up a tableID, or is a single
tableID used for the whole form? In other words:
if this is the form:
datasource is qryA which is based on tblA
form Field1 is bound to Field1 in qryA and the underlying field (in tblA) is
an ID field which has a lookup combo box using qryX (based on tblX) to show
the field value rather than the actual ID number
form Field2 from qryA
and the recordset that the form displays happens to have 30 records
then how many database connects are actually being used? Lots? Any way to
avoid a huge overhead of db connections?
Or is the problem (too many databases open) due to something altogether
different?
Hope this makes sense. Any help will be appreciated --
Chuck Flood