Skip to content

Allow_Undefined_State - dbComboFormDS

Determines if an undefined value is added to the combo list

Type: Property
Access: Read/Write
Data Type: Integer
Parameters: None

Syntax

Property Integer Allow_Undefined_State
Access Type Syntax
Read Access: Get Allow_Undefined_State to IntegerVariable
Write Access: Set Allow_Undefined_State to IntegerVariable/Value

Description

When entry_state is false, this adds the value to the top of the combo list. This is only used when a DD validation table is being used, allow_blank_state of the validation table is false, and the combo form's entry_state is false. The legend will be displayed when the combo is cleared (assuming that there is no default set in field defaults) but will generate an error when it is validated. This is used to force users to choose a selection instead of simply accepting what may be an improper default.

When a drop-down list is a non-edit list (Entry_state=False), users may only select choices from the list. What should happen when a form is cleared? Normally, the program will have a default value set in the DD's Field_Default section and that default will be chosen. If no default is provided, the first item in the list is selected. If the validation table allows blank items (allow_blank_state=True), that first item will be the value . If allow_blank_state is false, then the first item in the list is the default. This implies that a legal value is always selected. This type of behavior is most "Windows-like".

While this behavior is "Windows-like," some developers have noted that this is a poorly engineered solution for human data entry. Often users will ignore default values and just use whatever is provided. By setting Allow_Undefined_state to true, users will be forced to choose an item since the undefined selection will not be valid.

Default is false.