Yes: there is the possiblity of duplicates.
If you delete the record with the ID of (say) 74 - placing it in your
archive table instead - it would be possible later to add another record
that uses the value 74. Typically this is done with an Append query that
specifies the value, but it could also occur if 74 was the last value in the
table, and you compacted after deleting. The problem arises when you try to
delete #74 again later: you can't add it to your archive table, as you
already have a 74 there.
If your database is split, you also run into the problem where executing an
append query resets the AutoNumber's Seed to a value that is too low, so you
can't add any more records. (This is not really a problem about the archive
table.) More info:
Fixing AutoNumbers when Access assigns negatives or duplicates
at:
http://allenbrowne.com/ser-40.html
--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Salad" <oi*@vinegar.comwrote in message
news:13*************@corp.supernews.com...
I'm going to implement an archival database for my app. I have Table1 and
Table2. Table2 is a duplicate structure of Table1. I appended records
with "ID between 1 and 100", then "ID between 300 and 400" then "ID
between 225 and 250". It appears they keep the same ID.
Is there anything I need to be concerned about when adding records from
one table to another table with an identical structure when using
autonumbers?