Table Auto number Jumped from 2174 to 4027 when adding record

[oldlearner]

Hi all. A work colleague says she was inputting new records into a table and the auto number suddenly jumped by a couple of thousand numbers. Has anybody come across this before or know of a solution to realign the numbers. Any suggestions gratefully received.

[Homegrownandy]

Auto numbers should be internal and are not generally used or even seen by the user. What happens now if you add a new record? does it go up by one?

[CJ_London]

autonumber value should have absolutely no meaning other than as a unique id for a record. If you are using it for meaningful information such as an order or invoice number then it must be on the basis that you cannot rely on it being consecutive or even in order.

[oldlearner]

[QUOTE=Homegrownandy;357361]Auto numbers should be internal and are not generally used or even seen by the user. What happens now if you add a new record? does it go up by one?[the auto number is the primary key and the unique identifier and worked incremented correctly previously - but it just seems to have Jumped ]

[Homegrownandy]

I mean if you just add one record now.. Does it work as intended?

[oldlearner]

Yes it goes up by one. Just don't understand why it missed out a couple of thousand numbers

the auto number is the primary key and the unique identifier and worked incremented correctly previously - but it just seems to have Jumped

[Micron]

Aside from the unlikely probability that an operation added then deleted a whole lot of records, there are possibilities with respect to the autonumber seed or option settings. I wonder if you are working with replication? You might need to do a compact/repair regardless.
See here http://www.allenbrowne.com/ser-40.html

[oldlearner]

Hi - have already undertaken compact / repair and checked properties to ensure it had not switched to replication. Must just be a glitch. Does not seem to have had any adverse affects to the functionality of the database. Thanks for your comments