Properties
- Last Updated: February 11, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
The following table lists the available extended properties.
| Property name | Type | Access |
|---|---|---|
| HonorProKeys | logical | read/write at design timeread/write at runtime |
| Name | string | read/write at design timeread/write at runtime |
| Parent | COM-handle | read at runtime |
| Tag | string | read/write at design timeread/write at runtime |
| Visible | logical | read/write at design timeread/write at runtime |
The following table defines each property and how it can be used.
| Property | Definition |
|---|---|
| HonorProKeys | The default value of TRUE allows
the ABL code to process the GO, ENDKEY, HELP,
or TAB key stroke as each is defined.
Setting the value to FALSE causes the control to
process the key stroke without ABL code receiving notification that
the key stroke occurred. |
| Name | The Name property contains the name of the control. The name is
important because it identifies the control. You can use the control's name to get a
COM-HANDLE to the control (for example,
chCSSpin=chCFSpin:CSSpin, where CSSpin is the
control's name and chCFSpin is the control frame handle). The control
name associates event handlers with a control. |
| Parent | The Parent property is the com-handle (a pointer to the IDispatch interface) of the container in which the control resides. This property is set internally by ABL. |
| Tag | The Tag property is a user property that allows the user to store an arbitrary string value and retrieve it later. ABL does not use this property internally, and it is intended to give the user a way of storing application specific information with the control. This property is initialized to an empty string. |
| Visible | The Visible property determines and indicates
whether an ActiveX control is currently displayed. The Visible property
is distinct from, but influenced by, the Visible and Hidden attributes
of the Control-Frame widget. The Visible property will appear in
the Property Editor and can be set at design time. It defaults to TRUE.
The value set in the Property Editor determines whether the OCX
is initially displayed when the program is run, but can be overriden
by the value of the Control-Frame widget's Hidden attribute.Some
ActiveX controls are never displayed at runtime (for example, a
timer control.) For these controls, the Visible property will not
appear in the Property Editor and attempts to set the property at
runtime will have no effect. |