Huge jumps in AutoNumber

[RSW]

I inherited a database from someone else which has about 9000 records.

When sorted, one can see that the AutoNumbering starts at about 72K...then after a while there is a jump to about 134K...then after some more records the AutoNumber suddenly goes up to about 396K.

Does anyone know the most likely reason(s) that the numbering is like this?

Thanks in advance.

 

[Rabbie]

The only guarantee with autonumbering is that it will be unique. Thats why it should only be used as a primary key for a table. It does not go back and fill in gaps so if a lot of old records have been deleted you will get gaps in the sequence.

 

[boblarson]

It's possible that many records were deleted. But, it is also just one thing to be aware of that an Autonumber ONLY guarantees a UNIQUE number, not necessarily sequential nor even positive number.

 

[Dennisk]

I had to look at a database where an auto number was given to users as a call number then one day it jumped from 12,000 to 13,000,000.

The reason for this , the db probally became corrupted on the network as it was not even split FE/BE.

The moral is
1) Always use FE/BE with the FE on a local HD
2) NEVER expose the auto number to users.