For the third time since I built this database, the
Autonumber field (a primary key) has created duplicates
upon itself.
That is to say, after nothing significantly changed in the
Access application for many months at a time, one day, a
table just decides that I can't enter new records because
an autonumber is duplicated. Location hasn't changed, has
not been compacted recently. Given that Autonumber is a
field that cannot be updated (overwritten) by human touch,
so to say, why in the world does this happen?
Normally, I just create a replica of the original table
and append all of the records in the new table (with
Autonumber) and it's good to go.
Anyone have any idea why this keeps happening - or better
yet, how it can be prevented?? It would save me a lot of
time!
Thanks!
Andrew Smith - 05 Jan 2004 21:27 GMT
This happened to me a few weeks ago, and it was a real pain.
It is a known bug in Jet that has been supposedly fixed in the latest
service pack. However this did not sort it for me.
See these links:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;257408
http://members.iinet.net.au/~allenbrowne/ser-40.html
I changed the autonumber to "random" on the problem table, and it's been OK
since then.
> For the third time since I built this database, the
> Autonumber field (a primary key) has created duplicates
[quoted text clipped - 17 lines]
>
> Thanks!
Erica - 05 Jan 2004 22:55 GMT
Thanks - these were great references!
>-----Original Message-----
>This happened to me a few weeks ago, and it was a real pain.
[quoted text clipped - 33 lines]
>
>.