Error number 3260 giving fits...Help please...

[Chris D.]

To all Access Gurus

I have tried to look in all other places for an answer to a problem that I as well as other database programmers are having with Access 97. I have a database that three people are using at the same time. Every once in a while when someone is updating or adding a record, they get an "Error number 3260: Couldn't update; Currently locked by user 'Admin' on machine 'XXXX-XXXXX'" The user that gets the error sometimes gets kicked out and loses the changes they made. This of course makes the user very upset (rightfully so)

I have the locking set to no locks since Access 97 acts funky with setting the record locking to 'Edited record'. I have also looked at utteraccess.com (the one stop shop for answer to problems with Microsoft products) and I noticed alot of questions about this problem but no real solutions. I am at my wits end and would like some help. Thanks in advance

Chris Davidson

 

[GVaught]

Is your database split? If not, it should be. One database (back-end)
resides on a server that contains only the master tables. The other database
(front-end) resides on each user's machine. It contains the linked tables
from the back-end, queries, forms, reports, etc. The back-end must have
read/write/change permissions not only against the database file, but the
folder in which the database reside. Your tables should be set with 'edited
record'. With no locks, then whomever opens the tables first essentially
wins. Access 97 uses page locking. My understanding is if another users open
another record that is part of the original page file record opened after
the first record opened by the first user, the second user's changes will be
lost as the first user has locked the records from editing
..
Generally, database splitting and the proper permissions along with edited
records, generally solve this problem or prevents it from happen as often.

To all Access Gurus,

I have tried to look in all other places for an answer to a problem that

I as well as other database programmers are having with Access 97. I have a
database that three people are using at the same time. Every once in a
while when someone is updating or adding a record, they get an "Error number
3260: Couldn't update; Currently locked by user 'Admin' on machine
'XXXX-XXXXX'" The user that gets the error sometimes gets kicked out and
loses the changes they made. This of course makes the user very upset
(rightfully so).

I have the locking set to no locks since Access 97 acts funky with

setting the record locking to 'Edited record'. I have also looked at
utteraccess.com (the one stop shop for answer to problems with Microsoft
products) and I noticed alot of questions about this problem but no real
solutions. I am at my wits end and would like some help. Thanks in
advance.

 

[Chris D.]

Yes it is split. I have a mde front-end that is on the users PC and a mdb back-end that resides on the network. I also do not think that choosing the "edited record" setting is the way to go. Access has a nasty habit of locking records around the edit record as well when that is set. I am playing with the "Number of Update Retries" and "Update Retry Interval" to see if that might help elevate the problem. We do have a user that is on one of the slowest networks I have ever seen. I am optimistic that this will help for she seems to be the one that always locks up the table.

Thanks for your help so far. Should know by tomorrow afternoon if this works.