Currently Locked Error (Access 2000)

Topic

New Reply

I created a DB for data entry on which there are two people making entries at the same time. Periodically one user gets the error: Currently locked by user Admin on machine Comp2. Any ideas what maybe causing this, i searched the help but am still not sure what the problem may be.
Thanks.

Reply | Quote

Replies

If you mean they get the message while trying to enter/save data, it’s because the other user is editing the same record or the same page. If you’re using page locking this is more likely to happen, but you would have to give us more details before we can help you sort it out.

Reply | Quote

Thanks.
They are getting the error when they attempt to save. I do not have any locks, page nor record. They are entering records and never access the same records at the same time.
I included an autonumber on the form so that there should never be two identical records. But it looks like the following is happening. If they both open a new record at the same time, then both records fill in with the same autonumber. Could this be causing the problem during save. I assumed that when it was saving that it would populate the autonumber with the next available number.
Any suggestions for correcting this?
Thanks.

Reply | Quote

Personally I’d suggest you change it to Random rather than an incrementing autonumber…
Actually, I think I read a post earlier today where one of the Woody’s Gurus said that it’s a 1 in a billion chance of getting the same number twice…

HTH

Reply | Quote

Personally I’d suggest you change it to Random rather than an incrementing autonumber…
Actually, I think I read a post earlier today where one of the Woody’s Gurus said that it’s a 1 in a billion chance of getting the same number twice…

HTH

Reply | Quote

Whether you know it or not, you have recordlocking because that’s the way Access works. If you made no selection, the default is page locking, which locks a 2k page when the record is being edited. That means that any other records that fall into that 2k page are also locked from being saved. If the users are, in fact, getting duplicate *autonumbers*, rather than some unique key you’re generating, then you may be running into a bug in Access 2000 that should have been cured in O2k SR-3. Do you have that installed?

Are both these machines connected to the same back end database? You’re going to have to provide more in formation.

Reply | Quote

Whether you know it or not, you have recordlocking because that’s the way Access works. If you made no selection, the default is page locking, which locks a 2k page when the record is being edited. That means that any other records that fall into that 2k page are also locked from being saved. If the users are, in fact, getting duplicate *autonumbers*, rather than some unique key you’re generating, then you may be running into a bug in Access 2000 that should have been cured in O2k SR-3. Do you have that installed?

Are both these machines connected to the same back end database? You’re going to have to provide more in formation.

Reply | Quote

Thanks.
They are getting the error when they attempt to save. I do not have any locks, page nor record. They are entering records and never access the same records at the same time.
I included an autonumber on the form so that there should never be two identical records. But it looks like the following is happening. If they both open a new record at the same time, then both records fill in with the same autonumber. Could this be causing the problem during save. I assumed that when it was saving that it would populate the autonumber with the next available number.
Any suggestions for correcting this?
Thanks.

Reply | Quote

If you mean they get the message while trying to enter/save data, it’s because the other user is editing the same record or the same page. If you’re using page locking this is more likely to happen, but you would have to give us more details before we can help you sort it out.

Reply | Quote