[AccessD] Upsize errors

Stuart McLachlan stuart at lexacorp.com.pg
Wed Dec 21 23:02:28 CST 2005


On 21 Dec 2005 at 23:54, John Colby wrote:

> I am getting a TON of these kinds of errors.
> 
> CREATE UNIQUE INDEX ER_Reason ON tlkpEventReason(ER_Reason)
> 
> Server Error 1505: CREATE UNIQUE INDEX terminated because a duplicate key
> was found for index ID 3. Most significant primary key is '<NULL>'. Server
> Error 3621: The statement has been terminated.
> 
> I am confused as to how Access could have a unique index that SQL Server is
> finding a duplicate key for.  I have not gone looking yet.
> 

Was the index in Access on a field that had 'Required" set to "No". or was 
the index designed with "Ignore Nulls" set to "Yes"?
In either case, you could have Null records in the index and that appears 
to be what is causing the problem based on the above message.

 
-- 
Stuart





More information about the AccessD mailing list