Referential integrity problem

[Newman]

I have a table linked to six others with referential integrity and UpdateCascase and DeleteCascade checked. It works for five of them, but not with the sixth one.
What have I done wrong?

 

[bink_m]

Assuming Access <i>can</i> enforce referential integrity om six tables at a time, I think you should be a bit more specific. It may be that there's a logical impossibility in your references (like the database trying to force a field to be two different values at once)

Yours,
Martijn

 

[Newman]

It is hard for me to be more specific. If I knew where the diffrence lies between that particular tables versus the other five, I would have been able to pinpoint the problem and find the solution. My problem is that all the six tables are similar.
What I'm looking for is some hints on where I could look to find the problem. Your post is good 'cause it gave me 2 things to look for (unfortunatly, this is not the problem here I've been able to connect 6 tables and I don't see logical impossibilities neither).
Any other ideas?
Thank you!

 

[mdemarte]

unmatched query

Use an Unmatched Query to give you a list of records that don't match up.

For a one-to-many relationship, I usually list the many side. Most often, these become Orphan records -- meaning they don't have a Parent Record on the one side on which to be matched. Unfortunately, quite often there is little that can be done with them, unless you have a copy of the database with the missing record(s).

In my case, I had Orphan records because I had not enforced Referential Integrity initially with Cascade Update and Delete. Lesson learned.