HELP!!! - Autonumber Malfunction in Table

  • Thread starter Thread starter Latoya
  • Start date Start date
L

Latoya

I have a table that uses an autonumber as the primary key.
On two separate instances when trying to insert a new
record into this table through a form, I've gotten a key
violation error. When I went to the table to try to insert
information directly, I noticed that the table's
autonumber functionality was assigning a number that had
already been generated in the table. For example, the last
key value in the table is "412", but the table is
assigning "326" as the next primary key for the new row in
the table. However, "326" has already been assigned as a
primary key.

Does anybody know how and why this could be happening??? I
have been working with Access for about 7 years or so and
I'm floored by this problem. I have never seen this
before. I have the database set-up for a multi-user
environment, which I've done several times in the past.
The first time this problem occurred I created a duplicate
copy of the table and deleted the old one and the
autonumber started working properly again. However, this
problem happened again today. So, I changed the Autonumber
to "Random" instead of "Increment". I've searched through
the knowledgebase on microsoft.com and could not find a
reference to this issue.

Any suggestions, comments/insights would be helpful!
 
This happened to me a few months back. It's caused by a bug in Jet, and is
supposedly fixed by the latest service patch, but this did not work for me.
In the end I converted my autonumbers to random and they now work.

After I'd done this I was told that it may be necessary to reset the
autonumber seed on the affected table. See the following link from Allen
Browne for the necessary information:

http://members.iinet.net.au/~allenbrowne/ser-40.html

The following link is to a Microsoft article on this problem:

http://support.microsoft.com/default.aspx?scid=kb;en-us;257408&Product=acc2000
 
Back
Top