OrdCreate Function

 FUNCTION OrdCreate(
	cIndexFile,
	cOrder,
	cKeyValue,
	cbKeyValue,
	lUnique
) AS LOGIC CLIPPER

[ClipperCallingConventionAttribute(new string[] { ... })]
public static bool OrdCreate(
	Usual cIndexFile = default,
	Usual cOrder = default,
	Usual cKeyValue = default,
	Usual cbKeyValue = default,
	Usual lUnique = default
)

Parameters

cIndexFile (Optional)

Type: Usual
The name of the target index file, including an optional drive, directory, and extension. See SetDefault() and SetPath() for file searching and creation rules.
The default extension is determined by the RDD and can be obtained using DBOrderInfo(DBOI_INDEXEXT).
In RDDs that support production indexes , the production index file (that is, one with the same name as the database file) is assumed if cIndexFile is not specified.
If cIndexFile does not exist, it is created.
If cIndexFile exists, the INDEX command must first obtain exclusive use of the file.
If the attempt is unsuccessful because, for example, the file is open by another process, NetErr() is set to TRUE.
If the attempt is successful and the RDD specifies that index files can contain only a single order, the current contents of the file is overwritten with the new order.
If the RDD specifies that index files can contain multiple orders, the order is added to cIndexFile if it does not already exist; otherwise it is replaced.

cOrder (Optional)

Type: Usual
The name of the order to be created.
For single-order index files, the file name without an extension or path, is the default order name.
For multiple-order index files, the order name is required.

cKeyValue (Optional)

Type: Usual
The order key expression specified as a string.
This is the key expression that is stored in the index file and used for such purposes as locating key values and recreating the order.
Although cKeyValue is optional, it is highly recommended that you specify this argument. Without it, the order will be properly created using cbKeyValue, but the key expression will be stored in the index file as a NULL_STRING, rendering the order unusable for subsequent access.

cbKeyValue (Optional)

Type: Usual
The order key expression specified as a code block.
This code block is used to initially create the order.
If you do not supply cbKeyValue, it is macro-compiled from cKeyValue (for example, {||&cKeyValue}).
The data type of the key expression and all other limitations, including the length of the key and the key expression, are determined by the RDD.

lUnique (Optional)

Type: Usual
TRUE creates a unique order by including only those records with unique key values; FALSE uses all records in the database file.
If lUnique is omitted, the SetUnique() setting is used.Note that keys from deleted records are also included in the index, and may hide keys from non-deleted records.

Return Value

Reference