By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,827 Members | 2,177 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,827 IT Pros & Developers. It's quick & easy.

More on "cannot open another database" error

P: n/a
I have searched through previous threads regarding this error. I went
back through all my code to make sure I closed and set to nothing all
open db's and rs's. However, I still have one computer getting this
error. This problem does not occur with any other users - some of whom
use the database continuously.

The user logs in, then goes to the Add Invoice form - it's a fairly
simple form, single table recordset with a subform based on a single
table. When the user starts to enter the information, the On Dirty
event opens a table to look for the last voucher number entered so it
can generate the next consecutive number. As soon as the On Dirty
event it triggered, she gets the Cannot Open Another Database error.

I even tried clearing any open db or rs when On Dirty is triggered
using

If Not rs Is Nothing Then
rs.Close
Set rs = Nothing
End If
If Not db Is Nothing Then
Set db = Nothing
End If
I'm lost on this problem. I don't know what else to try.

Thanks in advance for any help you can give!

Jun 30 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Make sure that one computer has all the same references as all the
others (go into any block of code, choose Tools -> References).
Sometimes one computer in the chain will be lacking the references or
have older DLLs. Check to make sure the dates on COMDLG32.OCX and
COMCTL32.OCX in C:\Windows\System32 match the dates on all the other
computers also.

Jun 30 '06 #2

P: n/a
"Joanne" <en*********@yahoo.com> wrote in
news:11*********************@d56g2000cwd.googlegro ups.com:
I have searched through previous threads regarding this error. I
went back through all my code to make sure I closed and set to
nothing all open db's and rs's. However, I still have one
computer getting this error. This problem does not occur with any
other users - some of whom use the database continuously.


You don't say what version of Access is involved. If it were Access
97 (which is unlikely, I assume), it could be as simple as all the
machines except the problematic one having SR2 installed (or maybe
it was SR1) -- that service released doubled the number of table
handles from 1024 to 2048.

Given that it works OK on other machines, I'd guess the problem is a
software versioning problem. Check that the same versions of Jet and
Access are installed on all the machines.

And keep in mind that it's not merely a matter of DAO databases and
recordsets, but of *all* recordsets, including those open in forms,
subforms, combo boxes and listboxes. And that the table handles get
used up very quickly (a query with one source table uses up two
table handles, one for the source table, one for the query itself).

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Jun 30 '06 #3

P: n/a
Thank you both for your help. It was indeed a version problem. The
machine in question was running 2000, everyone else connects via the
terminal server which is running 2003.

Appreciate you pointing me in the right direction!
Joanne

Jul 5 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.