Can't create relationships (Driving me nuts!!)

[zlloyd1]

I am trying to make a simple database in Microsoft Access Professional Plus 2010, but it will not allow me to create a relationship properly because of. "No unique index found for the referenced field of the primary table". It will allow me to create a relationship between the two fields in question, but if I try to enforce referential integrity, it crashes and won't do it.... I have included screenshots of what is happening and would greatly appreciate any advice here, thanks in advance!!

[ssanfu]

To referential integrity between two tables, one table (the primary table) must have unique values. It doesn't have to be the primary key, but the field must have unique values. The other field shouldn't have unique values.

There are other problems... You have all three tables with the PK as "Case ID". (BYW, You shouldn't use spaces in object names.) This is a one to one to one relationship. (I don't think that is what you want)
Each table should have different names for the PK fields to avoid confusion. It doesn't make sense to have the table "Tracer Log" have a PK of "Case ID". I would name the PKs:

Table           PK Field name
---------------------------------
Contact      "Contact_ID"
Tracer Log   "T_Log_ID"
HUD           "Hud_ID"

If you wanted to referential integrity between Tables "HUD" and "Contact", with "Contact" being the primary table, you would add a field to the "HUD" table:
Name: "ContactID_FK"
Type: Long

Then drag the "Contact" table "Contact_ID" field to the "ContactID_FK" in the "HUD" table and set the referential integrity check box.

[zlloyd1]

To referential integrity between two tables, one table (the primary table) must have unique values. It doesn't have to be the primary key, but the field must have unique values. The other field shouldn't have unique values.

There are other problems... You have all three tables with the PK as "Case ID". (BYW, You shouldn't use spaces in object names.) This is a one to one to one relationship. (I don't think that is what you want)
Each table should have different names for the PK fields to avoid confusion. It doesn't make sense to have the table "Tracer Log" have a PK of "Case ID". I would name the PKs:

Table           PK Field name
---------------------------------
Contact      "Contact_ID"
Tracer Log   "T_Log_ID"
HUD           "Hud_ID"

If you wanted to referential integrity between Tables "HUD" and "Contact", with "Contact" being the primary table, you would add a field to the "HUD" table:
Name: "ContactID_FK"
Type: Long

Then drag the "Contact" table "Contact_ID" field to the "ContactID_FK" in the "HUD" table and set the referential integrity check box.