Checking Constraints

You can have your constraint checked by USoft Definer to see if you have made an error when defining it. This is standard practice.

If there are no errors, the checker will set Correct = Yes for your constraint. You cannot set this flag other than through the checker. The Correct = Yes setting will persist until you next make a change to the constraint, at which time you will need to check it again.

Constraints have an Active flag, that you can set or unset manually. Constraints that have Active = No are ignored at runtime.

Good practice is to AVOID having any constraints in your application that have Correct = No but Active = Yes.

To check a domain constraint:

1.	Define the domain constraint.

2.	Click Save to save work.

3.	Click the Check button.

If the domain constraint is correct, the checker will set the Correct = Yes flag.

If the constraint is not correct, a message is shown with an asterisk (*) at the position of the syntax error. Correct your work and repeat Steps 2 and 3 until the constraint is correct. If you cannot get it to work, you can keep your work without having it executed at runtime. To do that, leave Correct = No and set Active = No. Save.

4.	Click Save to confirm.

To check a table constraint:

1.	Define the table constraint.

2.	Click Save to save work.

3.	Click the Check button.

If the table constraint is correct, the checker will set the Correct = Yes flag.

4.	Click Save to confirm.