ChrisSedgwick
Registered User.
- Local time
- Today, 14:17
- Joined
- Jan 8, 2015
- Messages
- 119
Hi,
I'm not sure how this is happening, however I'm hoping that someone can help.
I have a table containing a list of customers and their contact details. The table includes an AutoNumber field which is set as the Primary Key and Indexed with No Duplicates.
We have over 650 records on this table, which has been entered via a form for around 2 years.
However, this morning when we've come to add a new customer, we saw an error message saying "Can't go to the specified record" then when we try to close the form it says that it couldn't add the record due to a potential duplicate in the table.
After examining the table, I tried to enter a new customer in the table itself. However, when I create a new line, the AutoNumber generates a number that has already been used. The record this morning tried to use number 86, which as you can probably guess from the amount of customers we have in our table, 86 was used some time ago.
I don't understand how this is happening considering that its a primary key and indexed and we've been using it for around 2 years with no issues or changes made.
Could anyone shed any light on this issue?
Thanks,
Chris.
I'm not sure how this is happening, however I'm hoping that someone can help.
I have a table containing a list of customers and their contact details. The table includes an AutoNumber field which is set as the Primary Key and Indexed with No Duplicates.
We have over 650 records on this table, which has been entered via a form for around 2 years.
However, this morning when we've come to add a new customer, we saw an error message saying "Can't go to the specified record" then when we try to close the form it says that it couldn't add the record due to a potential duplicate in the table.
After examining the table, I tried to enter a new customer in the table itself. However, when I create a new line, the AutoNumber generates a number that has already been used. The record this morning tried to use number 86, which as you can probably guess from the amount of customers we have in our table, 86 was used some time ago.
I don't understand how this is happening considering that its a primary key and indexed and we've been using it for around 2 years with no issues or changes made.
Could anyone shed any light on this issue?
Thanks,
Chris.