Hi Pew,
I believe it would and can - the unique conjoined key referential
integrity rules throttle the cartesian set created by the m-2-m
junction table..
I think I see need for, perhaps, a second & third conjoined UNIQUE
indexes, but maybe without another m-2-m junction..
I'm also tripping over your use of PolicyID instead of
PolicyTypeCode. Without seeing your subject data, I can't describe it
other than a unique key having: {PolicyTypeCode & CertID} and another
having {PolicyTypeCode & AgrmtID }.
Where these keys should live are another issue, but we need
clarity on which fields we should be using first, as they may just be
indexed table columns rather than m-2-m key junctions.
Post an access container of this (with test records) on your
Sharepoint and we can work this interactively.
Thanks,
Byron