Advantage Client Engine
Creates a new index order for the given table
AdsCreateIndex (ADSHANDLE hObj,
Handle of table or cursor. This can be an index order handle (the master index) if building a subindex.
Name of file for new index order. If this is NULL or if the base name is the same as the table and the table type is ADS_CDX, ADS_VFP or ADS_ADT, then a compound AutoOpen index file for hTable will be created/updated. If it is NULL and the table type is ADS_NTX, an NTX index file with the same base name as the table will be created. If no path is given, the index will be created in the same directory as the table.
Desired tag name. If NULL, then it is expected to be a non-compound index file. If the table type is ADS_ADT, then a compound index will always be created. If the tag name is NULL and the table type is ADS_ADT, the tag name will be the base name of the pucFileName parameter.
Index key expression. Can be any valid expression. Valid Advantage expressions can consist of field names, literal values, supported operators, and supported functions. For information on operators and functions supported in Advantage expressions, see Advantage Expression Engine.
Optional conditional expression (NULL or empty string indicates no conditional expression).
Optional while expression to use when building the index order (NULL or empty string indicates no while clause). This is a transient condition that stops the index build the first time it evaluates to False. Note that though there may be legitimate reasons to create indexes with a While expression, most filtering can be accomplished with the same or better performance by using AOFs.
A bit field for defining the options for index creation. The options can be ORed together into the bit field. For example ADS_COMPOUND | ADS_UNIQUE. The options are:
ADS_DEFAULT: If no options are needed, this constant (0) can be used.
ADS_COMPOUND: Create an index order (tag) within a compound index file. Note that this option is always set when the table type is ADS_ADT
ADS_DESCENDING: Create a descending index order.
ADS_UNIQUE: Create a unique index order.
ADS_CANDIDATE: This creates a unique index order that prevents duplicate data. On ADT tables, it is the same as the ADS_UNIQUE option. This can be used with Visual FoxPro tables (ADS_VFP) to create an index that can be used as a primary key and in referential integrity relationships.
ADS_CUSTOM: Create an empty index order. The user can add and remove keys via AdsAddCustomKey and AdsDeleteCustomKey.
ADS_BINARY_INDEX: Create a binary index. The index expression must have a logical result. This option cannot be combined with other options except for ADS_COMPOUND.
Return handle of new index order if successful.
AdsCreateIndex creates an index order list of sorted keys in the table the order is based on, referenced by the index key expression. The index key expression and "for" and "while" expression can be any expression supported by the Advantage Expression Engine.
AdsCreateIndex will replace existing indexes of the same filename if one exists.
The UNIQUE property of indexes is very different between DBF and ADT table types. With DBFs, an index order created with the UNIQUE property will only include records that are referenced by unique values. If two records result in the identical key value, then only one of the records will be referenced by the index. The second is simply never added, and no error is reported. This is the traditional Xbase behavior of the UNIQUE property.
With ADTs, an index order created with the UNIQUE property enforces all records in the table to be referenced via a unique key. When creating the index order, if a record is found that would cause a non-unique key to be placed in the index, an error will be logged in the Advantage error log. That error log entry will indicate the record number, the tag name, and the index name associated with the non-unique index value. Up to fifty of these unique key violations will be logged before the index creation will be aborted. If any records are not unique, an error will be returned, and the index will not be usable. If a unique index is successfully created, and a new record is inserted or updated in which the key produced from the record is not unique, an error will be returned and the record update will not be allowed. At that point, the record must be modified such that the key produced is unique. If the record change is not desired or possible, either the AdsCancelUpdate or AdsCloseTable API must be called to cancel the update of the record. Note that the AdsLookupKey API may be used to predetermine that a key is unique.
If you are using Visual FoxPro tables (table type ADS_VFP), then you can use the ADS_CANDIDATE option when creating the index. It provides the same unique behavior as the ADS_UNIQUE option on ADT tables. With ADS_ADT tables, the ADS_CANDIDATE and ADS_UNIQUE options are equivalent.
Subindexes are indexes built on the keys in another index, rather than all the records in a table. The index from which a subindex is created is usually a conditional index. This allows for a subset of the records in a table to be built into a new index.
Custom indexes can only be built on tables opened with the ADS_CDX or ADS_ADT option.
If a cursor handle is passed to this function, the index is considered to be a temporary index and is deleted when the cursor is closed.
Using AdsCreateIndex with an SQL Result Set
An index may be used on an SQL result set. The index created with AdsCreateIndex is on the new result set that is temporary, not on the original source table/tables that were queried to build the result set.
An error 5019 will occur if the second parameter, pucFileName, is null which indicates an index is being added to the auto-open index. Therefore, the pucFileName must not be null - a new filename for the index must be specified. After calling AdsCreateIndex, the new index file is open and ready for use.
For single table result sets, indexes that exist for the original table may be used after obtaining the result set. Therefore, it would not be necessary to use AdsCreateIndex on the result set if the index already exists for the original source table. If AdsCreateTable is used on a single table result set, tag names must be unique to the new temporary index as well as the auto-open index of the original source table.
Using AdsCreateIndex with Database Tables
When using AdsCreateIndex with database tables, the behavior of this API changes depending on the capability of the user who opened the table.
If the user is the ADSSYS user, the newly created index becomes part of the database. It will be automatically available to all users accessing the table.
If the user is not the ADSSYS user, the newly created index is temporary and it is automatically deleted when the table is closed. Since the index is temporary, the second parameter, pucFileName, cannot be NULL when calling this API. Otherwise a 5019 error will occur because the index cannot be added into the auto-open index file.
Create NTX index order (the table type of hTable must be ADS_NTX):
AdsCreateIndex( hTable, "x:\path\new.ntx", NULL,
"lastname+firstname", "lastname<'C'", NULL,
ADS_DEFAULT, &hIndex );
Create IDX index order (the table type of hTable must be ADS_CDX):
AdsCreateIndex( hTable, "x:\path\new.idx", NULL,
"lastname+firstname", "lastname<'C'", NULL
ADS_DEFAULT, &hIndex );
Create ADI index order with the tag name of "new" (the table type of hTable must be ADS_ADT):
AdsCreateIndex( hTable, "x:\path\new.adt", NULL,
"lastname+firstname", "lastname<'C'", NULL
ADS_DEFAULT, &hIndex );
Create either IDX, NTX, or ADI with a tag named "myindex" depending on the driver type:
AdsCreateIndex( hTable, "myindex", NULL,
"lastname+firstname", NULL, NULL, ADS_DEFAULT,
Create a compound index order when using table type ADS_CDX or ADS_ADT:
AdsCreateIndex( hTable, "x:\path\new", "tag1",
"lastname+firstname", NULL, NULL, ADS_COMPOUND,
Create a descending compound AutoOpen (structural) index order when using table type ADS_CDX or ADS_ADT:
AdsCreateIndex( hTable, NULL, "tag2", "lastname+firstname",
NULL, NULL, ADS_COMPOUND | ADS_DESCENDING,
Create a Subindex using a WHILE expression from a CDX index:
/* Create a "normal" index on the lastname field */
AdsCreateIndex( hTable, NULL, "TAG1", "lastname",
NULL, NULL, ADS_COMPOUND ,
/* Position to the first "Miller" in the lastname index */
AdsSeek ( hIndex1, "Miller", 6, ADS_STRINGKEY,
ADS_SOFTSEEK, &bFound );
* Create a While Subindex that contains only the "Miller"s. The index is
* built on the "DateOfHire" field. Since this index contains a while
* expression, the creation of the index will start at the current record
* instead of the top of the file. And since a controlling index was
* specified in the first parameter, this will result in a subindex that
* will read those records referenced by that controlling index. Thus,
* the index will get created starting with the first "Miller" in the controlling
* index and will contain all "Miller" records until it reaches a record in
* the controlling index that is not "Miller". By using the following code,
* the index creation will be fast because only the "Miller" records are
* considered for the index. This index should probably be used as
* a temporary index only due to the nature of While indexes and
AdsCreateIndex( &hIndex1, "subIndex", "TAG1", "DateOfHire",
NULL, "lastname = \"Miller\"", ADS_COMPOUND,
* Now use the new index to build another subindex, but limit the
* keys to contain only those records where the first name is "John".
* This type of operation might be useful if you need to build several
* different indexes where only the "Miller" keys are to be considered
* for the index.
AdsCreateIndex( &hIndex2, "subIndex", "TAG2", "DateOfHire",
"firstname = \"John\"", NULL, ADS_COMPOUND,
* Care should be taken when using subindexes rather than
* traditional record filters or Advantage Optimized Filters (AOFs)
* to view a subset of table. Though there may be legitimate
* reasons to use subindexes, most filtering can be accomplished
* with the same or better performance by using AOFs.