|
Home > Archive > MS Access Multiuser > April 2005 > locking errors 3187 + 3260: read & update
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
locking errors 3187 + 3260: read & update
|
|
| DavidVL 2005-04-06, 8:06 pm |
| Hi
I have a customer with an SBS 2003 Premium working currently only as
file/print server. No Exchange/ISA/SQL yet. There are 14 XP Pro clients
connected to 4 Access Points with 54MB Wifi G.
The server has a share containing an 80MB Access 2000 mdb database. The
database is accessed through serveral VB6 applications using DAO & ADO.
Everyday every client receives about 5-10 times either of the following to
errors:
<-- errors -->
Error Number: 3187
Could not read; currently locked by user 'admin' on machine 'WS11'
Error Number: 3260
Error Description: Could not update; currently locked by user 'admin' on
machine 'WS2'.
<-- errors -->
Some of the VB6 applications use DAO with the built-in VB6 control. Other
use the dataenvironment with Optimistic locking with client-side cursors. I
tried the different locking types but I see no difference.
Can somebody here tell me what I can try to do to make the errors go away or
atleast have less errors?
regards,
David
| |
| Scott McDaniel 2005-04-06, 8:06 pm |
| Are you using a datacontrol? Or are you manipulating data yourself?
Generally, you would prefer Optimistic locks (i.e. the record is only locked
at the exact instance it needs to be written).
"DavidVL" <David-NOSPAM@netcom.be> wrote in message
news:uvP9ZnQOFHA.580@TK2MSFTNGP15.phx.gbl...
> Hi
>
>
> I have a customer with an SBS 2003 Premium working currently only as
> file/print server. No Exchange/ISA/SQL yet. There are 14 XP Pro clients
> connected to 4 Access Points with 54MB Wifi G.
> The server has a share containing an 80MB Access 2000 mdb database. The
> database is accessed through serveral VB6 applications using DAO & ADO.
>
> Everyday every client receives about 5-10 times either of the following to
> errors:
>
> <-- errors -->
> Error Number: 3187
> Could not read; currently locked by user 'admin' on machine 'WS11'
>
> Error Number: 3260
> Error Description: Could not update; currently locked by user 'admin' on
> machine 'WS2'.
> <-- errors -->
>
> Some of the VB6 applications use DAO with the built-in VB6 control. Other
> use the dataenvironment with Optimistic locking with client-side cursors.
> I tried the different locking types but I see no difference.
>
>
> Can somebody here tell me what I can try to do to make the errors go away
> or atleast have less errors?
>
>
> regards,
>
> David
>
| |
| DavidVL 2005-04-06, 8:06 pm |
|
"Scott McDaniel" < scott@NO_SPAM_HEREth
edatabaseplace.net> wrote in message
news:iqSdnYm2L6is-8zfRVn-sA@comcast.com...
> Are you using a datacontrol? Or are you manipulating data yourself?
>
> Generally, you would prefer Optimistic locks (i.e. the record is only
> locked at the exact instance it needs to be written).
Yes I am using a datacontrol, the VB6 built-in. I didn't know you could
change the locktype wih this control.
I did the update just now and I'll let you know in a week or two how the
problem has evolved.
thanks
David
|
|
|
|
|