"Resetting" AutoNumber

I accidentally imported some data which had primary key field values (MSID)
starting in a much higher range than I want this field to go to. Essentially,
they were imported with 10000 range numbers, though I want to keep our
numbering within the hundreds range. (This is a meaningful number for us and
our clients to identify our records anonymously - and so we want to keep the
ranges low and relatively sequential). I've since deleted the data and
re-imported it with adjusted MSIDs, however, this is an autonumber field and
(as many of you reading would have anticipated) now when I go to enter new
records the MSID field starts populating back in the 10000 ranges. Is there
any way to make access forget about the importing error and start new
numbering back in the hundreds range? I've attempted "tricking" access with
creating clone fields and then swapping them out - but it just refuses to be
out-smarted. Thanks in advance!

Compacting the database should reset the autonumbers. It does in Access 2000.

Lauri S.

"kalexander" wrote:

I accidentally imported some data which had primary key field values (MSID)
starting in a much higher range than I want this field to go to. Essentially,
they were imported with 10000 range numbers, though I want to keep our
numbering within the hundreds range. (This is a meaningful number for us and
our clients to identify our records anonymously - and so we want to keep the
ranges low and relatively sequential). I've since deleted the data and
re-imported it with adjusted MSIDs, however, this is an autonumber field and
(as many of you reading would have anticipated) now when I go to enter new
records the MSID field starts populating back in the 10000 ranges. Is there
any way to make access forget about the importing error and start new
numbering back in the hundreds range? I've attempted "tricking" access with
creating clone fields and then swapping them out - but it just refuses to be
out-smarted. Thanks in advance!

My 2 cents...

If you care about what number is in autonumber then you should increment the
field another way. Autonumber frequently skips numbers among other things,
in other words it's not dependable.

Gina Whipp

"kalexander" wrote in message
...
I accidentally imported some data which had primary key field values (MSID)
starting in a much higher range than I want this field to go to.
Essentially,
they were imported with 10000 range numbers, though I want to keep our
numbering within the hundreds range. (This is a meaningful number for us
and
our clients to identify our records anonymously - and so we want to keep
the
ranges low and relatively sequential). I've since deleted the data and
re-imported it with adjusted MSIDs, however, this is an autonumber field
and
(as many of you reading would have anticipated) now when I go to enter new
records the MSID field starts populating back in the 10000 ranges. Is
there
any way to make access forget about the importing error and start new
numbering back in the hundreds range? I've attempted "tricking" access
with
creating clone fields and then swapping them out - but it just refuses to
be
out-smarted. Thanks in advance!

Oh right, works fine now thanks!

"LauriS" wrote:

Compacting the database should reset the autonumbers. It does in Access 2000.

Lauri S.

"kalexander" wrote:

I accidentally imported some data which had primary key field values (MSID)
starting in a much higher range than I want this field to go to. Essentially,
they were imported with 10000 range numbers, though I want to keep our
numbering within the hundreds range. (This is a meaningful number for us and
our clients to identify our records anonymously - and so we want to keep the
ranges low and relatively sequential). I've since deleted the data and
re-imported it with adjusted MSIDs, however, this is an autonumber field and
(as many of you reading would have anticipated) now when I go to enter new
records the MSID field starts populating back in the 10000 ranges. Is there
any way to make access forget about the importing error and start new
numbering back in the hundreds range? I've attempted "tricking" access with
creating clone fields and then swapping them out - but it just refuses to be
out-smarted. Thanks in advance!