Re: Duplicate Items in Item Master (and other data accidents)

<snip>
but finding the "guilty" party after
the fact doesn't erase the accident cost, it doesn't permanently slam the
back doors, and it doesn't train employees to keypunch flawlessly. There
will
always be the next data accident.
</snip>

After is after is after. Your product still alerts the farmer after the
horses escaped the barn. It doesn't lock the door. To do that you would
have to add constraints to the database. And triggers for more involved
situations. The problem with that is, if you throw a write error out
because of a violation would Infor's code be able to handle that? For
example would this code:
C WRITE(E) IPI100IM
C*
C IF NOT %ERROR AND OPERRFLAG=*BLANKS
C Z-ADD 1 S_IIML02
C EXSR SMVTOW
C ELSE
C END
C ENDSR
say "dude, there's a constraint violation"?

Let's use another example. The OP asked about duplicate records. Would
your solution catch that? For example I add a duplicate key outside of
infor. Would the DBA then get notified? Or is the product more focused
on individual field errors, like ranges and what not?

Rob Berendt