Autonumber Issue

  • Thread starter Thread starter mattc66 via AccessMonster.com
  • Start date Start date
M

mattc66 via AccessMonster.com

Hi All,

I have an ID field that is an AutoNumber. This database has been working well.
Know all of the sudden the AutoNumber is trying to re-assigning exsiting
numbers. It's failing as would be expected. The next Autonumber should be
157763, but it's trying to start again in the 30098 range.

Does anyone know how to fix this issue?

Thanks
Matt
 
That sounds truly bizarre Matt... you don't think that you may be on your
way to a corruption do you?

have you checked that somehow your autonumber field hasn't become an "allow
duplicates" non primary key field, which can happen if you import data into
it and certain conditions are met.

Damian.
 
Hi All,

I have an ID field that is an AutoNumber. This database has been working well.
Know all of the sudden the AutoNumber is trying to re-assigning exsiting
numbers. It's failing as would be expected. The next Autonumber should be
157763, but it's trying to start again in the 30098 range.

Does anyone know how to fix this issue?

Thanks
Matt
Click to expand...

What version of Access, and what service packs have been applied? (You
can find out using Help... About Access). This is a known bug that's
been in several versions. For example, see the knowledge base article
http://support.microsoft.com/kb/291162/en-us.

John W. Vinson [MVP]
 
I found my problem and resolved it. It was an external upload that was
appending the ID fld. Correct it and then made an Append table to get the
Autonumber to start at the next available number.

Matt
Hi All,
Click to expand...
[quoted text clipped - 7 lines]
Thanks
Matt
Click to expand...

What version of Access, and what service packs have been applied? (You
can find out using Help... About Access). This is a known bug that's
been in several versions. For example, see the knowledge base article
http://support.microsoft.com/kb/291162/en-us.

John W. Vinson [MVP]
Click to expand...
 
Yup, that would do it. I know it's possible to programmatically set a value
in an autonumber column and if Access does not reject it as a duplicate it
will use this new number as the starting point for a new series.

Rod
 
Back
Top