Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
|A single word||
||Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".|
You can specify that the search results contain a specific phrase.
Topics that contain the literal phrase "cat food" and all its grammatical variations.
Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.
Two or more words in the same topic
|Either word in a topic||
|Topics that do not contain a specific word or phrase||
|Topics that contain one string and do not contain another||
|A combination of search types||
- Forms Designer controls and tools
- Attachments control
- Button control
- Calendar control
- Chart control
- Checkbox control
- Combo Box control
- Comfill control
- Convert Form Layout tool
- Date control
- Decimal control
- Dynamic Form control
- Embedded Viewer control
- File control
- Frame control
- Graph control
- Grid view tool
- Group control
- HTML Editor control
- HTML Viewer control
- Image control
- Label control
- Link label control
- List Builder control
- Marquee control
- Notebook tab control
- Notebook control
- Radio Button control
- Selection tool
- Script control
- Subform control
- Table column control
- Table control
- Text area control
- Text control
- Timer control
- Visualization control
- Web Preview tool
- Wrap label control
Use this control to add a checkbox that displays and enables users to update the contents of a Boolean (logical) field, which can evaluate to true, false, unknown, or null.
To place a checkbox on a form, click Checkbox and then click the form.
Be sure to put the name of the database field or variable that you want to associate with this control into the Input property.
|Name||Specify a unique identifier for the object on the screen. (Optional)
This name is used by external applications, such as RAD, to dynamically change the properties of the object.
|X||Specify the object’s horizontal position based on the left edge of the object.|
|Y||Specify the object’s vertical position based on the top edge of the object.|
|Width||Specify the width of the object in alignment grid units.|
|Height||Specify the height of the object in alignment grid units.|
|Visible||Select this option to make the object visible on the form. Clear the check box to hide the object from view on the form.|
|Visible Condition||Specify an expression to override the Visible property when that expression evaluates to true.|
|Caption||Specify a text caption for the object.|
|Caption Condition||Specify an expression to override the Caption property when that expression evaluates to true.|
|Input||Specify the database field or variable to associate with this control.|
|Accessible Name||Specify a component name for use with accessibility software. (Optional)
Note: This function is only supported by the Web client.
If no name is present, the Web client defaults to looking for a nearby label to use for the name of the component. For buttons, check boxes, or radio buttons, it uses the component’s text. Accessibility software can query the Web client to get this information, and use it to present it to the user in a variety of ways. For example, speech simulation software says the name and the type of component when the component has focus.
|Accessible Description||Specify a component description for use with accessibility software. (Optional)
Note: This function is only supported by the Web client.
If no description is present, the Web client defaults to looking for a nearby label to use for the name of the component. For buttons, check boxes, or radio buttons, the Web client will use the component’s text. Accessibility software can query the Web client to get this information. The client uses that information to present data to the user in a variety of ways. For example, speech simulation software will say the name and the type of component when the component gets focus, based on the settings in the Accessible Name and Accessible Description fields.
|Tab Stop||Specify the tab sort order for this field. By default, the TAB key navigates the focus on a form from top to bottom and left to right. Objects that have a non-zero Tab Stop are visited first, in ascending order. For a button, file, radio button or check box, you will almost always use the default of 0.|
|Foreground Color||Select the text color from the drop-down list.|
|Read-Only||Select this option to disable editing capabilities and provide only viewing access to the field. Give read–only fields a tab–stop value of –1 to prevent users from tabbing into them.|
|Read-Only Condition||Specify an expression to override the Read-Only property when that expression evaluates to true.|
Specify the size of the scrolling region used to view array entries. A scroll bar appears beside the fields to allow users to view the array entries.
- If a field is assigned an Array Length of 5, the form stacks five fields vertically to allow users to view the five array entries.
- If Array Length is set to -1, the form dynamically creates as many fields as there are entries in the array.
- If the Input data type is scalar, only a single text box appears.
Note: The screen object must be associated with an array data structure.
The default is 0, which means one vertical line of information appears.
|Data Changed Event||Specify the option number (such as Button ID) to call if the data contained in the object changed. This sends an event to the display RAD application.|
Creating and editing forms
Using the drawing canvas
Forms Designer properties view
Enabling HTML in forms
Forms Designer best practices
Web client forms
Building accessible forms
Accessible Web client forms