Violation of referential integrity rule (one to many relationship)

[zkrucz]

My company provides a service of testing drinking water backflow devices (the device prevents drinking water from backing into the source – one direction flow only)<br>I am starting to set up a new database which would track all tests on various backflow devices and I have 3 Tables.<br><br>Address List with unique PWS ID#s (Public Water System)<br>Backflow Device Table (Unique device Serial#)<br>And, Table# which list all the tests.<br><br>I have created the 3 Tables as shown below.<br><br>The problem that I am facing is that when try to link the Backflow Device List and the Address List, I can’t enforce the referential integrity rule. The error message states that the Backflow Devices List violates the rule.<br>However, I was able to enforce the referential integrity rule when I linked The Backflow List to my Table3 Tests.&nbsp; I get a similar error when I attempt to link Table3 to the Address List (this time the error refers to Table# as the one violating the rule.<br>&nbsp;<br>Please advise how to resolve this problem so that I can link all three tables enforcing the referential integrity rule.<br><br>

[CJ_London]

enforcing integrity requires a child (the many) has to have a parent (the one). The implication is either you have already created records before you tried to enforce integrity and some of those records either do not have an associated parent record or the field is not populated. Or you have different datatypes for the two fields - perhaps you are using lookups in the table

[zkrucz]

enforcing integrity requires a child (the many) has to have a parent (the one). The implication is either you have already created records before you tried to enforce integrity and some of those records either do not have an associated parent record or the field is not populated. Or you have different datatypes for the two fields - perhaps you are using lookups in the table

Thank you! The problem was the missing records. Life is good!