Specifies whether the recognition engine should create read-only equivalent controls where identified on the dynamically created form.
object.CreateReadOnlyControls = [boolean]
Where object is an object expression that evaluates to one of the controls in the Applies To list, and boolean is a boolean expression that evaluates to either True or False, as described in Settings.
Newlook Smartclient
Newlook Server
Usually, read-only (or protected) fields render as labels in the GUI form. However there may be times when you want to render them as read-only versions of the equivalent input controls.
For example, let's say you have an Edit Customer Details screen in your application, where a users can update various customer fields. Once changes have been made and the screen is sent back to the host, a confirmation screen is sent back. The fields that were previously entry-capable are now protected. Usually these protected fields would be generated as labels on the form. However it is possible to generated those fields as read-only versions of the input fields used in the edit screen.
Figure 1. Protected fields displaying as labels (default display)
Figure 2. Protected fields displaying as read-only text boxes.
To display read only equivalents in your form the following conditions must be met:
This property can be used to create read-only versions of check boxes, option buttons, text boxes or combo boxes.
You can set this property globally for all forms in your project via Rules | General Rules in the Advanced Display Options section.
Setting |
Description |
True |
Protected fields that have been manually identified with an entry capable category type in Identify will generated as read-only controls. |
False |
Protected fields will generate as labels. |
© 2004-2021 looksoftware. All rights reserved.