Articles in this section

See more

Why do I get the error "There are no primary or candidate keys in the referenced table..." when upsizing?

Avatar
SSW Admin
  • Updated
Follow

During upsizing from Access 2000/2002/2003 to SQL Server 2000 you might encounter a Microsoft Upsizing Wizard error similar to this one:

Server Error 1776: There are no primary or candidate keys in the referenced table 'Test1' that match the referencing column list in the foreign key 'Test3_FK00' (SQL Server 2000)
Server Error 1750: Could not create constraint. See previous errors (SQL Server 2000)
or Microsoft Upsizing Wizard quits without any errors displayed (SQL Server 2000)
or a relationship will not be enforced (SQL Server 2005)

Q506841_1.png

This occurs when you have a related field that does not have a primary or unique index:

Q506841_3.pngQ506841_2.png
Figure: Upsizing will fail if you do not have primary or unique indexes defined on a related field

You should add primary or unique key on the field and/or change relationship type to 'Enforce Referential Integrity' and/or 'Cascade Update Related Fields'.