Reads - Enabled

If you want the permitted value enforcement for read statements for all of the tables in the databases to be handled by the DBMS.

By enabling the DBMS to control the permitted value enforcement, you are requiring all applications (CA Gen or not) that will be reading tables in the generated database to adhere to the same permitted value rules.

If you allow the database to handle the permitted value violations, there will be no action taken for the reads within the CA Gen application.

Reads - Disabled

If you want the permitted value enforcement to be handled at the database level and you want CA Gen to do the enforcement.

This is a good selection if there are no permitted values in the database, or if you do not want the DBMS to enforce the permitted values for READ statements.

Creates/Updates - DBMS

If you want the permitted value enforcement for row creates and updates for all tables in the databases to be handled by the DBMS.
By enabling the DBMS to control the permitted value enforcement, you are requiring all applications (CA Gen or not) that will be creating or updating rows in any of the tables in the generated database to adhere to the same permitted values.
If you select this option, an SQL return code will be returned to the CA Gen application within the create statement (when permitted value violation exception) and you will handle it in the procedure logic. See the chapter “Designing the Procedure Logic.”

Creates/Updates - CA Gen

If you want CA Gen to handle the permitted value enforcement.

This is a good selection if there are no permitted values in the table, or if you do not want the DBMS to enforce the permitted values for create and update statements.