The following keywords set attributes on index level. They must be set directly after the column keywords, if those are present in the INT file.
Index keywords are grouped per index. If you want to set an index keyword, the index must be identified first (Index_Number), then you can set one or more index keywords for that particular index. The keywords will apply to the last Index_Number that was specified.
Most of the keywords discussed here will be automatically set by the driver and will never be added to the intermediate file.
There are two types of indexes that can be defined in the intermediate file: Indexes that are defined at the server and those that are defined only in DataFlex. You can use a mix of the two index types on a table. Defining an index in DataFlex only is useful when using database views or an index that is only used sporadically.
The Structure_End logic favors server indexes. It will try to create as many indexes at the server as possible. If you have defined indexes only in DataFlex because they are seldom used, a Structure_End on the table will create these indexes at the server.
When the index exists at the server itself, only use the following intermediate file keywords:
When defining indexes that exist on the DataFlex side only, use the following intermediate file keywords:
Please note that you can define indexes on the DataFlex side only. This means that there is no physical index defined in the database. You can program in DataFlex as if the index actually exists.
Be aware that since no actual physical index exists, the performance when accessing that table by the index will be greatly affected (i.e. it is not going to be fast).