Can mandatory field violations be caught? - Progress Community

Loading

Skip to Main Content

Can mandatory field violations be caught?

How to catch database table records containing mandatory fields where, the initial value of the mandatory fields is set to the unknown value (?)? Why doesn't a Progress.Lang.AppError CATCH block catch such an error?

Jul 20, 2016
Knowledge

Title

Can mandatory field violations be caught?

URL Name

Can-mandatory-field-violations-be-caught

Article Number

000187386

Environment

Product: OpenEdge Version: 11.6.x OS: All supported platforms

Question/Problem Description

Creating database records containing one or more mandatory fields, where the initial value for those fields is the unknown value (?) causes an error.
How can such an error be trapped?

Steps to Reproduce

Clarifying Information

A field with the mandatory attribute set is added to a database table.
The initial value of this field is set to the unknown value (?).
An attempt to create a record, set up as defined above, reports the following error:
"**<file-name>.<field-name> is mandatory, but has unknown (?) value. (110)".
Adding a Progress.Lang.AppError CATCH block does not catch the error.

Error Message

Defect Number

Enhancement Number

Cause

Resolution

Add a Progress.Lang.SysError CATCH block to trap for records being created that contain fields that are mandatory and have an initial value of the unknown value (?).

In the following code example, a new field is added to the Customer table of the sports2000 database. The field is defined as mandatory and its initial value is set to the unknown value (?):

DEFINE VARIABLE myInt AS INTEGER INITIAL 4 NO-UNDO.

DO myInt = 1 TO myInt:
CREATE Customer.
VALIDATE Customer.
END.

CATCH myAppError As Progress.Lang.AppError:
MESSAGE "Application error an application error occurred " VIEW-AS ALERT-BOX.
END CATCH.

CATCH mySysError AS Progress.Lang.SysError:
MESSAGE "SysError " mySysError:GetMessage(1) VIEW-AS ALERT-BOX.
END CATCH.

CATCH myError AS Progress.Lang.Error:
MESSAGE "Error " myError:GetMessage(1) VIEW-AS ALERT-BOX.
END CATCH.

In this example, the error reported is "** <file-name>.<field name> is mandatory, but has unknown (?) value. (110)". The error can be caught by either the Progress.Lang.SysError or the Progress.Lang.Error CATCH blocks. In this example since the Progress.Lang.SysError CATCH block comes before the Progress.Lang.Error CATCH block, the Progress.Lang.SysError CATCH block catches the error. The Progress.Lang.AppError CATCH block does not catch this error because this error is an error thrown by an ABL statement as opposed to an error thrown by the application.

Workaround

Notes

References to other Documentation:

OpenEdge Development: ABL Reference, Class, Interface, and Enumeration Reference: "Progress.Lang.AppError class".
OpenEdge Development: ABL Reference, Class, Interface, and Enumeration Reference: "Progress.Lang.SysError class".
OpenEdge Development: ABL Reference, Class, Interface, and Enumeration Reference: "Progress.Lang.Error class".
OpenEdge Development: ABL Reference: "CATCH statement".
OpenEdge Development: Object-oriented Programming, Programming with Class-based objects: Raising and handling error conditions: "Structured and traditional error handling".

Keyword Phrase

Last Modified Date

7/20/2016 2:58 PM

OpenEdge DeploymentOpenEdge ArchitectureOpenEdge DevelopmentOpenEdge General DiscussionsOpenEdge Pro2OpenEdge RDBMS

Drop Files

Upload FilesOr drop files

Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Loading

Can mandatory field violations be caught? - Progress Community