Re: ADO recordset doesn't see DB changes
- From: "Bob Barrows [MVP]" <reb01501@xxxxxxxxxxxxxxx>
- Date: Mon, 14 May 2007 08:54:42 -0400
Neil B wrote:
Interesting information regarding the way the Jet Engine works.
I read the intro to the articles and they indicated that the problem
you think is the culprit arises if you have 2 connection paths to the
database. The way my app is set up there is only 1 connection path to
the DB (that is I only open the database once) which both recordsets
use. I gathered from what I read that this problem required 2
connections.
I'm not sure, but I think the provider is unable to support more than
one cursor at a time per connection. I suspect what is happening behind
the scenes when you open the second recordset is that, instead of
returning an error, it is opening a second implicit connection to
provide the second cursor, thus leading to the delayed-write issue.
Also, when I ran the app in debug mode I stopped after recordset2 did
it's changes and stepped thru the recordset1 read code a record at a
time (I was not in a hurry) and the changes were not reflected. I
would think the database would have been updated by then no matter
how lazy it was. There was nothing else running on the system at the
time.
Am I interpretting this right?
I'm not sure, but it couldn't hurt to try the remedy suggested by the
second article, could it?
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.
.
- References:
- Re: ADO recordset doesn't see DB changes
- From: Bob Barrows [MVP]
- Re: ADO recordset doesn't see DB changes
- From: Bob Barrows [MVP]
- Re: ADO recordset doesn't see DB changes
- Prev by Date: Re: ADO OpenSchema( adSchemaPrimaryKeys , ...)
- Next by Date: Re: ADO OpenSchema( adSchemaPrimaryKeys , ...)
- Previous by thread: Re: ADO recordset doesn't see DB changes
- Index(es):
Relevant Pages
|
|
