Could you tell me what I need to do to get this not to give me an error?

The changes you requested to the table were not successful because they 
would create duplicate values in the index, primary key, or relationship.  
Change the date in the field or fields that contain the duplicate date, 
remove the index, or redefine the index to permit duplicate entries and try 
again.

thanks.
-- 
Denise B.

Denise

As the error message suggests, your table has data that would invalidate a 
key, an index or a relationship.

You'll need to find/fix that duplicate data before re-trying to index the 
field(s).

Regards

Jeff Boyce
Microsoft Access MVP

-- 
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

"Denise" <Denise@discussions.microsoft.com> wrote in message 
news:374F883F-DB44-4B13-9C60-0A9E1EF248A9@microsoft.com...
> Could you tell me what I need to do to get this not to give me an error?
>
> The changes you requested to the table were not successful because they
> would create duplicate values in the index, primary key, or relationship.
> Change the date in the field or fields that contain the duplicate date,
> remove the index, or redefine the index to permit duplicate entries and 
> try
> again.
>
> thanks.
> -- 
> Denise B. 

As I learned from my many errors....

I think that the most common case of seeing that message is when entering a 
new record which has a PK field value which duplicates that of a previous 
record.   
 

Need to run a 'match' query to find duplicate record.
-- 
Build a little, test a little.


"Fred" wrote:

> As I learned from my many errors....
> 
> I think that the most common case of seeing that message is when entering a 
> new record which has a PK field value which duplicates that of a previous 
> record.   
>  
> 

Karl, 

I've seen this message lots of times, and 100% of them were the following 
case: 

I was referring to when the duplicate "record" is not even a record 
yet...e.g. someone just entered a new record with a manually entered PK, and, 
when you they to move off the new record (i.e. when Access woudl otherwise 
enter it) , Access rejects it and gives this error message.