cannot open any more databases

[Debbie Gilbert]

When running a report..I get the message "Cannot open any more
databases." Run-time error 3048... Has anyone seen this message
before?

[Allen Browne]

If this is Access 97, the solution was to download Service Release 2 from:
http://support.microsoft.com/support...cks/Office/97/

If you have the pack or are running a later version, the problem might be
related to the number of domain aggegate calls you are making, e.g. if the
report's query or controls call DLookup(), DMax(), etc. If that's the case,
post back and we will give you a replacement for DLookup().

It's also important to dereference your object variables in your code. For
example, if you have code that uses CurrentDb and OpenRecordset, ensure you
close the recordset and set your object to nothing. This kind of thing:
rs.Close
Set rs = Nothing
Set db = Nothing

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Debbie Gilbert" <dg******@tasconcrete.com> wrote in message
news:47**************************@posting.google.c om...

When running a report..I get the message "Cannot open any more
databases." Run-time error 3048... Has anyone seen this message
before?

[Pieter Linden]

dg******@tasconcrete.com (Debbie Gilbert) wrote in message news:<47**************************@posting.google. com>...

When running a report..I get the message "Cannot open any more
databases." Run-time error 3048... Has anyone seen this message
before?

Are you opening recordsets or creating variables and not explicitly
destroying them by setting <object>= Nothing after you finish your
code? That would cause you to run out of resources...

[Phil Stanton]

I have had the same problem with A2K, in spite of dereferencing everything
and usind ELookup queries etc rather than DLookup. The problem is compounded
by List Boxes, Combo Boxes, & subforms each of which is running an SQL which
gets reported as "Cannot open any more databases."

Phil
"Debbie Gilbert" <dg******@tasconcrete.com> wrote in message
news:47**************************@posting.google.c om...

When running a report..I get the message "Cannot open any more
databases." Run-time error 3048... Has anyone seen this message
before?

[David W. Fenton]

dg******@tasconcrete.com (Debbie Gilbert) wrote in
<47**************************@posting.google.com >:

When running a report..I get the message "Cannot open any more
databases." Run-time error 3048... Has anyone seen this message
before?

This error message is sometimes erroneous in that it's actually
*table handles* that you're running out of. There's a pretty good
discussion of this problem (interpreting the error message both
literally and as evidence of insufficient table handles) at:

http://dbforums.com/arch/42/2003/6/804659

I don't know that anyone reached a solution in that discussion, but
it raises a whole bunch of issues that you need to consider.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[David W. Fenton]

al*********@SeeSig.invalid (Allen Browne) wrote in
<3f**********************@freenews.iinet.net.au> :

If this is Access 97, the solution was to download Service Release
2 from:
http://support.microsoft.com/support...cks/Office/97/

If you have the pack or are running a later version, the problem
might be related to the number of domain aggegate calls you are
making, e.g. if the report's query or controls call DLookup(),
DMax(), etc. If that's the case, post back and we will give you a
replacement for DLookup().

It's also important to dereference your object variables in your
code. For example, if you have code that uses CurrentDb and
OpenRecordset, ensure you close the recordset and set your object
to nothing. This kind of thing:
rs.Close
Set rs = Nothing
Set db = Nothing

According to the discussion in:

http://dbforums.com/arch/42/2003/6/804659

using a recordset variable for a recordsetclone opens implicit
database references. So, this:

Dim rs As DAO.Recordset

Set rs = Me.RecordsetClone
rs.FindFirst [whatever]
If Not rs.NoMatch Then Me.Bookmark = rs.Bookmark
Set rs = Nothing

will (in A2K) cause an implicit database reference to be created
that is not released at the end.

The solution is to not use a recordset variable, but to use a With
block:

With Me.RecordsetClone
.FindFirst [whatever]
If Not .NoMatch Then Me.Bookmark = .Bookmark
End

That does not have the same problem.

It's also a good lesson -- don't use a Set statement with a
variable if a With block is usable in the same context.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Allen Browne]

David, thanks for posting the link to this discussion.

The behavior makes no sense to me, but I am still seeing the same result in
Access 2003. It is something that needs further investigation, but does
appear to be an issue with this error.

Appreciated.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"David W. Fenton" <dX********@bway.net.invalid> wrote in message
news:94***************************@24.168.128.86.. .

al*********@SeeSig.invalid (Allen Browne) wrote in
<3f**********************@freenews.iinet.net.au> :

If this is Access 97, the solution was to download Service Release
2 from:
http://support.microsoft.com/support...cks/Office/97/

If you have the pack or are running a later version, the problem
might be related to the number of domain aggegate calls you are
making, e.g. if the report's query or controls call DLookup(),
DMax(), etc. If that's the case, post back and we will give you a
replacement for DLookup().

It's also important to dereference your object variables in your
code. For example, if you have code that uses CurrentDb and
OpenRecordset, ensure you close the recordset and set your object
to nothing. This kind of thing:
rs.Close
Set rs = Nothing
Set db = Nothing

According to the discussion in:

http://dbforums.com/arch/42/2003/6/804659

using a recordset variable for a recordsetclone opens implicit
database references. So, this:

Dim rs As DAO.Recordset

Set rs = Me.RecordsetClone
rs.FindFirst [whatever]
If Not rs.NoMatch Then Me.Bookmark = rs.Bookmark
Set rs = Nothing

will (in A2K) cause an implicit database reference to be created
that is not released at the end.

The solution is to not use a recordset variable, but to use a With
block:

With Me.RecordsetClone
.FindFirst [whatever]
If Not .NoMatch Then Me.Bookmark = .Bookmark
End

That does not have the same problem.

It's also a good lesson -- don't use a Set statement with a
variable if a With block is usable in the same context.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc