Re: Cannot open database error
- From: "Ralph" <nt_consulting64@xxxxxxxxx>
- Date: Thu, 10 Dec 2009 09:28:16 -0600
"primeMover" <primeMover@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3A9E9950-5CD3-4B57-80AE-D62ABAF4C2C2@xxxxxxxxxxxxxxxx
ModifyAnd of course you need to verify that the user of the database has
permissions on the folder containing the database file.
Yes, I double-checked that.
[I'm wrapping my reply to several posts here - otherwise this will turn into
a bush rather than a tree. <g>]
Just to clarify:
You said your snippet is from a wrapper, so can I assume that your
application has only 'One' ADODB.Connection object? That the principle
elements - Cursor, database, ... that make up an ADO connection don't
change, and you are only opening and closing on use? ie, you are not
"newing" a new ADODB.Connection everytime?
Within the above scenario are you also keeping it open while opening
multiple Recordsets? Or do you only have one Recordset open (and thus the
Connection object open) at one time? This is only of mild interest because
while ADO uses connection pooling, ADO does create a new Jet session for
every connection to Jet.
So are we talking about - dying on the request for a 4th session, or the 4th
time we request a new session? (Or whatever I was trying to say. <g>)
How rapidily are you opening and closing this connection. Jet sessions do
have some latency. Just for grins - insert a 'pause'.
[I know I seem to be unduly harping on the subject of having only one
ADODB.Connection object. That is because I've seen more than one a common
cause for 'bizzare' issues in the past. Use/abuse the ADO connection pool -
that's why it is there.]
As an aside be sure to read this if you haven't yet:
"How to keep a Jet 4.0 database in top working condition"
http://support.microsoft.com/kb/303528/
Note you are using a translator dll with your configuration - I don't
believe for a moment that is the source of your problem - but doesn't hurt
to check.
Your report that another test application works just fine, assuming the same
general architecture, is rather disturbing. <g> As that suggests there is
something within the code for that application that is unique. Did you also
test opening and closing a connection 4 times?
Oh, is the database located on each box, or is it accessed remotely?
Other than insuring you are only using one ADODB Connection object, and
playing with delays, I don't have anything more concrete to offer. I like to
think I debug in a logical orderly professional manner, but when faced with
a situations like this, I often end up just clicking and playing driven more
by hope than reason. <g>
If you do find the cause - please return and let us know.
-ralph
.
- References:
- Re: Cannot open database error
- From: Ralph
- Re: Cannot open database error
- From: Bob Barrows
- Re: Cannot open database error
- From: Ralph
- Re: Cannot open database error
- From: primeMover
- Re: Cannot open database error
- From: Bob Barrows
- Re: Cannot open database error
- From: primeMover
- Re: Cannot open database error
- Prev by Date: Re: Cannot open database error
- Next by Date: Re: Cannot open database error
- Previous by thread: Re: Cannot open database error
- Next by thread: Re: Cannot open database error
- Index(es):
Relevant Pages
|