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

Autonumber Problem

P: n/a
We have a database which has recently started driving us nuts. It, and
some of its ancestors, have been in use for about 8 years and, until last
January, everything seemed fine. However, in the last couple of months, it
has been sending messages demanding that it be repaired and compacted
several times a week.

This has never happened before.

Recently, we have found that several tables with autonumbers are generating
duplicate values. For example, we have one table with about 20,000
records. It has an autonumber column that sometimes generates the same
number twice. For example, in a couple of instances, 329 has shown up
twice when the next autonumber should be about around 20,000.

Is this autonumber problem known? I have not been able to find references
to it. Is there a quick fix to it such as applying a service pack?

Thanks.

--PatF
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a

"Patrick Fleury" <pf*****@removethissbcglobal.net> wrote in message
news:Xn**********************************@128.135. 12.171...
We have a database which has recently started driving us nuts. It, and
some of its ancestors, have been in use for about 8 years and, until last
January, everything seemed fine. However, in the last couple of months, it has been sending messages demanding that it be repaired and compacted
several times a week.

This has never happened before.

Recently, we have found that several tables with autonumbers are generating duplicate values. For example, we have one table with about 20,000
records. It has an autonumber column that sometimes generates the same
number twice. For example, in a couple of instances, 329 has shown up
twice when the next autonumber should be about around 20,000.

Is this autonumber problem known? I have not been able to find references
to it. Is there a quick fix to it such as applying a service pack?

Thanks.

--PatF

The first thing you should do is backup the database or save it with a
different name.

Did you compact the database? A database should be compacted occasionally,
but AFAIK the database must be failing if it is requesting to be compacted
frequently.

Check the properties in the tables to be sure the Auto number has the proper
settings, Make sure the Index is set to Yes(No duplicates)

Charlie O'Neill

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.