By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,853 Members | 1,027 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,853 IT Pros & Developers. It's quick & easy.

Problems with autonumber field

P: n/a
Dear reader,

By append a new record to a table I always expect the next higher value in
the range of the autonumber field.

But sometimes if I have deleted same records from a table the behaviour of
the autonumber field is changed.

By append a record, not the highest value of the autonumber field will be
used but one of the deleted records and after the gap is closed an already
existing autonumber field will be used. And then an error message pops up
"The change you requested to the table were not successful because they
would create duplicate value in the index, primary key, or relationship."

Is there a reason why the autonumber field changes his behaviour, to
implement a lower number in the range of number already exist.

Is there a solution to avoid this?

Thanks for any help.

Kind regards,

Simon van Beek
Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
This can occur, but should be fixable. See if these articles will help.

http://support.microsoft.com/default...b;en-us;257408
http://support.microsoft.com/default...b;en-us;291162
http://support.microsoft.com/default...b;en-us;209710
http://support.microsoft.com/default...b;en-us;884185

--
Wayne Morgan
MS Access MVP
"S. van Beek" <S.******@HCCnet.nl> wrote in message
news:42*********************@reader20.nntp.hccnet. nl...
Dear reader,

By append a new record to a table I always expect the next higher value in
the range of the autonumber field.

But sometimes if I have deleted same records from a table the behaviour of
the autonumber field is changed.

By append a record, not the highest value of the autonumber field will be
used but one of the deleted records and after the gap is closed an already
existing autonumber field will be used. And then an error message pops up
"The change you requested to the table were not successful because they
would create duplicate value in the index, primary key, or relationship."

Is there a reason why the autonumber field changes his behaviour, to
implement a lower number in the range of number already exist.

Is there a solution to avoid this?

Thanks for any help.

Kind regards,

Simon van Beek

Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.