Astonish behavior of 2010 AutoNumber’s Seeds

[Khalid_Afridi]

Compacting and recovering of Access-2007 database with Access-2010 format gives ridicules results.
The Auto numbers seeds drop below the next seed numbers and give duplicate error, no new record can be Added to the effected table.

See this Thread...

 

[Galaxiom]

This error has been covered before and is fixed by reseeding the autonumber.

http://www.access-programmers.co.uk/forums/showthread.php?s=&threadid=45181

Actually on reading closer this might not be what you want. Try searching similar temrs on this site beccause I have seen this problem fixed here.

 

[Khalid_Afridi]

This error has been covered before and is fixed by reseeding the autonumber.

http://www.access-programmers.co.uk/forums/showthread.php?s=&threadid=45181

Actually on reading closer this might not be what you want. Try searching similar temrs on this site beccause I have seen this problem fixed here.

Thanks for reply,
I just want to know where is the potential mess where the autonumber changes to the lowest number seeding in Ms-Access 2010 format. In 2007 and earlier versions I did not face this problem.

I noticed something special while compacting the database with 2010 format.

• 
  The tables which were not sorted with ascending order by its autonumbers key drops its seeding number to the last record.
  
  i.e
  1001
  1002
  1005
  1006
  1004
  1003

Starts the seeding numbers from 1004 instead of 1007, which is already issued before compacting and gives duplicate error.

The Ms-Access 2010 consider the last seed in this case 1003 as the highest seed which is wrong, and the highest seed in this case is 1006 autonumber, so it should give the next highest seed as 1007.

I don't know why this happens? I think I am missing something in Access 2010.