Helmut,

> Is there any simple way to find out at least one (the
> first) record, which causes the constraint error, to
> show the user which record he should inspect to look
> for the reason of the error message.

Interesting request. I dont think that there is a "simple" way to do
this.

I remember a discussion quite some time ago about making the error
message variable information available directly. I still have my
ideas about how to do this sitting in my todo list :-)

If the raw variable information was made available then it may be
possible to use the constraint and entity names from the specific
error to retrieve the related records and display something meaningful
to the user.

Even with the information required to select the related records,
showing something useful to the user may be complicated. What if the
related records belong to an intersection entity, containing nothing
useful (just surrogate key values). This means putting in place some
sort of internal identification of the each potential problem so that
you can retrieve the appropriate tables/fields for the user to know
what the problem is.


Geoff Worboys
Telesis Computing