Kbase P113140: RELEASE NO-ERROR does not always suppress error messages
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
02/02/2006 |
|
Status: Unverified
SYMPTOM(s):
RELEASE NO-ERROR does not always suppress error messages
Violating the unique constraint on an index returns error 132 despite using NO-ERROR
** <file-name> already exists with <field/value...>. (132)
Error messages cannot be suppressed
Using VALIDATE NO-ERROR works as expected
CAUSE:
This is expected behaviour. For RELEASE, Progress ignores the NO-ERROR clause when validating the record before any changes that the record may have are saved.
To avoid damaging indexes, an error is raised so that the block is backed out.
FIX:
Use VALIDATE NO-ERROR in place of RELEASE NO-ERROR.
Please refer to solution P20090 for more information.