Previous Topic

Next Topic

Book Contents

Book Index

Form Designer Surrogate Data Combo Properties

Navigator > Setup > Form Designer > Layout tab > Component Editor > Properties tab

See also Form Designer Component Properties for properties common to different component types.

The following properties are available for Surrogate Data Combo Components:

BorderStyle

Set the border style for the combo, to Single or None.

DittoSibling

You can select another combo to be paired with this component. When components are paired, the user can press Ctrl+' to copy the value of the paired component into the component.

Note: Both components must have the same LookupSource.

This can be useful where you have related components, such as Period From and Period To fields, or Date From and Date To fields.

Hint

The Hint text to be displayed when the mouse hovers over the component.

IgnoreGridParent

When True, when the component is on a grid it will not be checked to see if it is unconnected.

IndexName

Select a field to index the table. This determines the order of the drop-down list.

LabelCaption

The text to be displayed beside the Combo box.

LabelVisible

When False, the Label Caption will not be displayed.

LabelWidth

Set the width of the Label Caption.

LookupFilter

You can enter a filter to apply when data is added to the drop-down list.

ReadOnly

When True, the user cannot edit the component on the form.

TabOrder

Set the sequential tab order for components, when the Tab key is pressed in the form.

TabStop

When True, this component will be included in the tab order. When False, the Tab key will not stop at this component.

Visible

When True, the component will be displayed on the form.

Hint: For Combos backed by Memory Tables, the Display Inactive button in ButtonsAvailable will only work if the memory table has two indexes: one called "PrimaryKey", and one called "ActivePrimaryKey", where "ActivePrimaryKey" is a key on a boolean field called "Inactive". At design time, the combo and the memory table must use the non-active index in the IndexName property.

For example, if the Primary Key is CustomerCode, then Index1 could be "Customer" and Index 2 could be "ActiveCustomer".