access - primary key table problem

There continues to be a problem, as the first URL Roy quoted indicates.

http://support.microsoft.com/default...b;en-us;884185

Some of the other autonumber bugs were fixed by previous service packs.

This is still a bug in SR8.

(And I think I tested it using a new table in a new A2000 database)

(david)



"Douglas J Steele" wrote in message
...
"RoyVidar" wrote in message
...
journigirl wrote in message
:
On a table with 1004 records - when I open the record, it knows there
are 1004 but when trying to add a new one, the primary key index
does not assign 1005 but rather goes to 1 (and of course it won't
store because of a duplicate key - thank goodness). Exit the table,
repeat above, and this time it points to 2 ...and so on...
Does anyone know how to reset the index to the bottom of the table or
replace the table with a corrected one without having to go thru the
whole database and change all the record connections and field
names? Thanks.

Autonumbers aren't meant to be sequental numbers. You are expected to
see intervalls due to cancelled records etc, but having it restarting
from one isn't that common. Check out this link
http://support.microsoft.com/default...b;en-us;884185
Perhaps try it out on a copy? I think, if this table is a parent table
in a parent-child relationship, you will need to remove the
relationships while doing this.

And if it's not an Access 2003 database, have all the service packs been
installed? This was definitely a problem when Access 2000 was first
released, but it was supposedly corrected in one of the SPs.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)