I have an ID field in a table set to AutoNumber data type, and it's the
primary key (Indexed: Yes, no duplicates). When I create a new record,
Access re-uses an ID number that already exists in the table for that ID
field, and of course I get the message that a conflict exists in the index,
primary key, etc.

Any ideas where to start looking for the issue here? It's Access 2007. Is
this a new "feature" of 2007 -- where AutoNumber uses a number that is
already in use in the table? It is very strange.

Steve

Try "Compact and Repair..."


"Steve Vincent" <(E-Mail Removed)> wrote in message
news:CDA17E00-3BAA-4909-9C49-(E-Mail Removed)...
>I have an ID field in a table set to AutoNumber data type, and it's the
> primary key (Indexed: Yes, no duplicates). When I create a new record,
> Access re-uses an ID number that already exists in the table for that ID
> field, and of course I get the message that a conflict exists in the
> index,
> primary key, etc.
>
> Any ideas where to start looking for the issue here? It's Access 2007.
> Is
> this a new "feature" of 2007 -- where AutoNumber uses a number that is
> already in use in the table? It is very strange.
>
> Steve

Did it, fixed it, thank you!

"Norman Yuan" wrote:

> Try "Compact and Repair..."
>
>
> "Steve Vincent" <(E-Mail Removed)> wrote in message
> news:CDA17E00-3BAA-4909-9C49-(E-Mail Removed)...
> >I have an ID field in a table set to AutoNumber data type, and it's the
> > primary key (Indexed: Yes, no duplicates). When I create a new record,
> > Access re-uses an ID number that already exists in the table for that ID
> > field, and of course I get the message that a conflict exists in the
> > index,
> > primary key, etc.
> >
> > Any ideas where to start looking for the issue here? It's Access 2007.
> > Is
> > this a new "feature" of 2007 -- where AutoNumber uses a number that is
> > already in use in the table? It is very strange.
> >
> > Steve
>
>

Steve, here's an explanation of some of the causes for this problem:
Fixing AutoNumbers when Access assigns negatives or duplicates
at:
http://allenbrowne.com/ser-40.html

As Norman pointed out a compact/repair sometimes fixes this problem. You can
use the code in the article above to fix other cases.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Steve Vincent" <(E-Mail Removed)> wrote in message
news:E2BDC46D-8717-472C-807B-(E-Mail Removed)...
> Did it, fixed it, thank you!
>
> "Norman Yuan" wrote:
>
>> Try "Compact and Repair..."
>>
>>
>> "Steve Vincent" <(E-Mail Removed)> wrote in message
>> news:CDA17E00-3BAA-4909-9C49-(E-Mail Removed)...
>> >I have an ID field in a table set to AutoNumber data type, and it's the
>> > primary key (Indexed: Yes, no duplicates). When I create a new
>> > record,
>> > Access re-uses an ID number that already exists in the table for that
>> > ID
>> > field, and of course I get the message that a conflict exists in the
>> > index,
>> > primary key, etc.
>> >
>> > Any ideas where to start looking for the issue here? It's Access 2007.
>> > Is
>> > this a new "feature" of 2007 -- where AutoNumber uses a number that is
>> > already in use in the table? It is very strange.
>> >
>> > Steve