Subject | [IBO] Version 4.7.16 Error Message changes? |
---|---|
Author | Paul Hope |
Post date | 2007-09-17T08:13:13Z |
Hi
As this message hasnt appeared via email after 2 attempts and several
days I am now posting it on the Yahoo site directly - I'm wondering
if its broken - again.
On storing a record Firebird generates an exception 'Cannot end-date
a Principle dentist'. This used to be reported to the user like
that ie 'Cannot end-date a Principle dentist' - now I get
_______________________
ISC ERROR CODE:335544517
ISC ERROR MESSAGE:
exception 2
Cannot end-date a Principle dentist
STATEMENT:
TIB_Statement:
"<TApplication>,HFMMain.fDenFind.DentistForm.iboqDen.IBOqriboqDen.<TIB
_UpdateSQL>.<TIB_Statement>
STATEMENT:
TIBOInterna.
_________________________
The users will think the end of the world has come ;-)
Is there an easy way of switching this behaviour off? I've tried
using OnError to present my message and setting RaiseException to
false but the message is then followed by a 'Record not located for
update' error.
If it isnt possible already I think it would be a great idea if a
global option at connection or session level could be used such that
only the error message is presented and not the code or anything else.
Regards
Paul
As this message hasnt appeared via email after 2 attempts and several
days I am now posting it on the Yahoo site directly - I'm wondering
if its broken - again.
On storing a record Firebird generates an exception 'Cannot end-date
a Principle dentist'. This used to be reported to the user like
that ie 'Cannot end-date a Principle dentist' - now I get
_______________________
ISC ERROR CODE:335544517
ISC ERROR MESSAGE:
exception 2
Cannot end-date a Principle dentist
STATEMENT:
TIB_Statement:
"<TApplication>,HFMMain.fDenFind.DentistForm.iboqDen.IBOqriboqDen.<TIB
_UpdateSQL>.<TIB_Statement>
STATEMENT:
TIBOInterna.
_________________________
The users will think the end of the world has come ;-)
Is there an easy way of switching this behaviour off? I've tried
using OnError to present my message and setting RaiseException to
false but the message is then followed by a 'Record not located for
update' error.
If it isnt possible already I think it would be a great idea if a
global option at connection or session level could be used such that
only the error message is presented and not the code or anything else.
Regards
Paul