×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
