Re: Could not update; currently locked error
- From: "Bob Barrows [MVP]" <reb01501@xxxxxxxxxxxxxxx>
- Date: Tue, 19 Feb 2008 15:22:08 -0500
Andriy wrote:
I am not quite understand how the switching of ADODB from
apartment-threaded to free-threaded may help me to prevent the lock
error. Could you explain me please?
I was just reacting to the fact that you were using multiple threads. I
was not sure if this would have an effect on your lock problem.
With Jet, you also need to be aware of Jet's "delayed-write"
optimization. Jet caches database writes to improve performance:
http://support.microsoft.com/?kbid=240317
http://support.microsoft.com/kb/200300
I wonder if there any way to tell Jet to wait and retry again if a
record is locked?
Not that I know of. You have to handle this in your application code.
--
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:
- Could not update; currently locked error
- From: Andriy
- Re: Could not update; currently locked error
- From: Bob Barrows [MVP]
- Re: Could not update; currently locked error
- From: Andriy
- Re: Could not update; currently locked error
- From: Bob Barrows [MVP]
- Re: Could not update; currently locked error
- From: Andriy
- Could not update; currently locked error
- Prev by Date: Re: Could not update; currently locked error
- Next by Date: Re: Command object and batching stored procedure calls
- Previous by thread: Re: Could not update; currently locked error
- Index(es):
Relevant Pages
|
|
