RE: Constraint Violations

[Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>]

>My problem is that the error indicator coming on could be a
>one of many RI
>Violations on the same table. It could also be a record lock.

You're not alone there, my friend.  That's why it's not so easy to make a
generic error handler.  When the error flag comes on, you need to check the
status code to see what sort of error you're dealing with.  Then call the
handler appropriate to the error.  So I have a pop-up window for "Record in
use by xxx/xxx/xxx - try again in 1 minute or call xxx" and I have a dump
and "File in use by xxx/xxx/xxx - operation cancelled" for object locks,
etc.  Some things get retried automatically, some require the user to wait
and try again and some are fatal (communication line errors.)

RI problems require the user to go back and correct the entered data.  I
have been toying with a cross-reference file using the condition name as the
key, and then user-updateable "help text" to tell the user what to do when
the constraint is violated.  Haven't got anywhere with it yet.

>I'm trying to
>validate 1 byte flags to only allow certain values. I guess I
>could use the
>values keyword in the DDS, but I thought I'd expand my horizons.

A trigger _may_ be more helpful here in that the trigger could detect if the
call is interactive and pop up a display telling the user they've tried an
invalid combination.
  --buck