There is no duplicate, so why does access tell me there is?

[Jonathan A. Cheyne]

Hi there guys,
On a simple database I built about a year and a half ago, and use regularly,
I today needed to add some more records. The first one went on fine, after
that however, I tried to add a second, and recieved an error message saying
"The changes you requested to the table were not successful because they
would create duplicate values in the index, primary key, or relationship."
(Error 3022). I know that the data I am inputting is not a duplicate of
anything else in the table (or even the entire database), and to prove this,
tried inputting random data, only to be presented with the same error
message. I'm not a particularly accomplished user of Access, so would
appreciate any help that could be offered.
Thanks a bunch,

Jonathan A. Cheyne

 

[Paul Shapiro]

Try the Compact & Repair option, which rebuilds indexes from the data. If
the problem persists, try creating a new blank db and importing everything
from the current db.

"Jonathan A. Cheyne" <[email protected](no spam please, we''re
british)> wrote in message
news:[email protected]...

 

[MikeJohnB]

For database pre 2007 (not to sure of 2007), the auto number field used for
indexes, used to get corrupted and the database used to jump back into the
autonumber field within a gap made previously by deleted data. This meant
that when the autonumber field eventually filled the gap, the next autonumber
became a duplicate. (I have come accross this problem)

The way around this is to run the compact and repair facility (but make sure
you make a copy of your database first).

I hope this helps??

 

[Jonathan A. Cheyne]

Woops.
Sorry guys, just noticed a screw-up i made when adding a new field recently
which caused this.
thanks for your help anyways!