RE: Active record code referential constraint.

[rob@xxxxxxxxx]

Trigger sounds like it.

If I make IID and IPROD the primary keys then there's nothing stopping 
there being both an "active" and an "inactive" row for a single item 
number - thus duplicate item numbers in the file.
If I then add to the complexity by leaving those the primary key but then 
adding a unique constraint on item number, there's still nothing stopping 
a new row from appearing in the child for an inactive item number.
All that will happen in the alternative is that the child file will know 
that item is now inactive.

Looks like an insert trigger on the child, which verifies that the active 
record code in the parent is active, will have to be the solution.


Rob Berendt