Form Designer: General Control Properties

The following general control properties belong to all types of controls:

Property	Description
Form Type	Specifies the name of the form. For each feature class, there is a default form. You can define multiple forms per feature class.
System Category	System category properties cannot be changed.
Name	All controls related to a database attribute are named like the attribute. For example, the text box FID. All other names start with the suffix "$", such as $FIDREFERENCE or $FORMULA1 or $FORMULA2.
ClassName	For example: TextBox
Base Category
Caption	This caption is displayed in front of the input box.
GroupLocked	Specifies that the controls are visible but locked for one or more user groups. Select the group whose members are not allowed to use this control.
GroupSuspend	Specifies that the controls are invisible for one or more user groups. Controls can be suspended for certain user groups. Select the group whose members are not allowed to use this control.
HideAtGrid	Hides a control in Table View mode. True = hidden, false = shown.
NextControl	Defines the tab order. Each time a user presses <TAB> or <ENTER>, the cursor moves to the control (input field) that you can define here. This way, you can control the order of inputs.
ToolTipText	Help text that is displayed when the cursor hovers over the input field.
Database Category
ColumnDesc	Description of the attribute
ColumnName	Attribute name
Help Category	Assigns a help topic to a control. The topic is displayed if you press F1 while the cursor is on the control. The properties are the same as for the form Help. See also Designer Menu: Options
Help Context	Assigns a help topic, such as application_introduction.htm.
HelpFilename	For AutoCAD Map 3D toolset: Specifies the help file. For example, autocad_map3d.chm. Note: If you define no HelpFilename for a control, the HelpFilename of the form is used.
HelpURL	For Infrastructure Application Extension : URL of the Help topic. For example, index-app-extension.html.
Specific Category
ClientSideUniqueCheck	True = if the user enters a value, the system checks whether the value is unique for the feature class. Note, that this property does not apply to the Oracle database property. Example: Set this value to True to import data from Excel that may contain identical values. In this case, you would have set the Oracle property to Non Unique to allow the import from Excel. However, you want to prevent the user from entering new values that already exist. The default is False.

More properties are shown in the following sections.