Unique ID/Duplicate Entry

[baconroll]

I have a database which multiple users access. The recordID filed is a unique
field/autonumber. When the user creates a new record, it populates the next
available no. and assigns it to that record. There have been a couple of
instances recently when two people have accessed the same record. eg. User1
creates a new record and access assigns the no. 12345. They entered all their
information and when they go to exit, it says that another user has entered
information into the same record and do they want to drop/discard changes. I
thought that as this was a unique field, this shouldn't happen. Any advice
would be most welcome. Thank you.

 

[Bernd Gilles]

hallo baconroll,

I have a database which multiple users access. The recordID filed is a unique
field/autonumber. When the user creates a new record, it populates the next
available no. and assigns it to that record. There have been a couple of
instances recently when two people have accessed the same record. eg. User1
creates a new record and access assigns the no. 12345. They entered all their
information and when they go to exit, it says that another user has entered
information into the same record and do they want to drop/discard changes. I
thought that as this was a unique field, this shouldn't happen. Any advice
would be most welcome. Thank you.

you can try to use replication-id as the record-id instead of a long-integer auto-value.
this should be a really unique number (in most cases)

 

[baconroll]

Hello, thanks for your reply.

I guess my question really was, why did this happen and is there a situation
where this could happen i.e. 2 people pressing create new record at exactly
the same time. I just wondered if this was a bug in access or not as I have
been unable to re-create this scenario.

 

[Richard]

Hello, thanks for your reply.

I guess my question really was, why did this happen and is there a situation
where this could happen i.e. 2 people pressing create new record at exactly
the same time. I just wondered if this was a bug in access or not as I have
been unable to re-create this scenario.

You don't mention if your database is split? or sharing across a network. In
the menu under options goto advance and look for default open mode, shared or
exclusive. Also default record locking.

Richard