FAQ700-184: Why AutoNumber shouldn't be used in MultiUser databases (A

[dotolee]

Has anyone had to implement this?
I found one record in my database that's been completely duplicated (including the PK) and I'm trying to figure out why / how. The PK is an autonumber.
It's a split database with 3 users.
This FAQ seems to be talking about how to prevent the error about duplicates being created from appearing. But has anyone implemented this to successfully prevent MS Access from actually creating duplicates?
I ask only because I've been doing a lot of research and there seems to be multiple things to try to prevent duplicates and I want to prioritize.
Thx

 

[JoeAtWork]

The FAQ only speaks about preventing duplicate ID numbers. It doesn't really address your problem where the entire record was duplicated. That problem is more likely due to either a corrupt database, or some problem with your code.

Do you create records strictly with bound forms, or do you have code that creates the record?

 

[dotolee]

In this case, it's a bound form.
I included another comment in my previous post re: how this supposedly happened ... per the end user, she opened a previously saved record, modified the comments field and resaved. It was after this event that she noticed the duplicate.
I'm not using any subforms here either....and the autonumber is set to "increment".

 

[TheAceMan1]

How are ya dotolee . . .

. . . and how are you saving? . . . a button with code . . . what!

This could happen if you had a button that appended the record, giving the impression of saving and causing the duplicate.

See Ya! . . . . . .

Be sure to see thread181-473997
Also faq181-2886

 

[dotolee]

Hi again theAceman!

I just created a form using the wizard and am using the navigation tools at the bottom of the form to move through the recordset. I didn't create any additional buttons. To save, they just navigate away from the current record.
Is this the equivalent of appending?