Jump to content
  • 0

Table Conflicts with Integrity Rules


pmcfarlain
 Share

Question

I'm trying to enforce referential integrity with some tables in my app so that I can cascade update/delete records but I keep getting this error:

 

2009893565_ScreenShot2021-07-09at2_20_01PM.png.e511be67250a0556011a0d15c6c38fd2.png

The parent field is an autonumber and the related field is a unique integer. It's a one-to-one relationship with an inner join. Here's the relationship settings.

522900329_ScreenShot2021-07-09at2_19_54PM.png.589827395f95765f1ae4f219a9767fa8.png

Any ideas?

Link to comment
Share on other sites

4 answers to this question

Recommended Posts

  • 2

You may check if there are ID records from your related table that are not present from your parent table. All referenced child records should be present on your parent table to enable the referential integrity.

Link to comment
Share on other sites

  • 0

I'd prefer to keep it unique as these tables should be one-to-one rather than one-to-many but if I need to change it to make this work that's not the end of the world. However, even after turning off unique on the child table, I'm still getting the same error message.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...