Indexes Tab¶
How To Access
Index Tab¶
Allows you to add modify or delete indexes for the table.
Index No: Displays the currently selected DataFlex index number. Fields that make up the index structure are listed in the grid on the right. Use the spin button to select an index.
Delete Index: Drops the selected index from the table.
Add New Index: Allows you to add a new index to the table. The available fields are listed in the Select a field popup dialog box.
Segment: The fields that comprise the index segment.
CS: Check CS if the index values are case sensitive. Leave this selection unchecked if indexes are case insensitive.
Desc: Check Desc if the sorting order of the segment is descending. Leave this selection unchecked if the sorting order is ascending.
Add Segment: Adds a new segment to the current index. The fields are selected using the Select a field popup dialog box. Adds the segment at the end of the segment list.
Insert Segment: Adds a new segment to the current index. The fields are selected using the Select a field popup dialog box. Adds the segment in the middle of current segment list.
Select a field popup dialog box: The Select a field popup dialog box is displayed when adding an index, adding an index segment, or inserting an index segment. It lists available fields in the table.
Delete Segment: Deletes an existing segment.
Legacy Index Support¶
When Mertech launched its products in 1997, most RDBMS did not allow for creation of ASC or DESC index segments or support case sensitive indexes. Mertech created a unique approach using INVERSE key values to support this functionality. However, most new databases now allow these features, so the use of inverse keys is no longer needed. These options are still available but not as the default. To turn them on, check the following options.
Create Inverse Keys: Creates inverse key columns in the table.
Create Old-Style Inverse Key Names: In an earlier version of Flex2SQL, Mertech modified how inverse keys were named. Select this option to use the older inverse key naming conventions. Unless you require explicit field names for inverse keys on the SQL server, this option is not needed.