Click or drag to resize

OrdCondSet Function

Set the condition and scope for an order.

Namespace:  XSharp.RT
Assembly:  XSharp.RT (in XSharp.RT.dll) Version: 2.10
Syntax
 FUNCTION OrdCondSet(
	 cForCondition AS USUAL,
	 cbForCondition AS USUAL,
	 lAll AS USUAL,
	 cbWhileCondition AS USUAL,
	 cbEval AS USUAL,
	 nInterval AS USUAL,
	 nStart AS USUAL,
	 nNext AS USUAL,
	 nRecord AS USUAL,
	 lRest AS USUAL,
	 lDescend AS USUAL,
	 lAdditive AS USUAL,
	 lCurrent AS USUAL,
	 lCustom AS USUAL,
	 lNoOptimize AS USUAL
) AS LOGIC
View Source

Parameters

cForCondition
Type: Usual
A string that specifies the for condition for the order.  This string is returned by DBOrderInfo(DBOI_CONDITION, [<cIndexFile>], <cOrder>).  If you do not need this information, you can specify a NULL_STRING.
cbForCondition
Type: Usual
A code block that defines a condition that each record within the scope must meet in order to be processed.
> This condition (not <cForCondition>) is the one that is actually used to create the order.   Unlike the while condition and other scoping information, the for condition is stored as part of the index file and is used when updating or rebuilding the order with DBReindex().  Any limitations on the for condition are determined by the RDD (see the "RDD Specifics" appendix in the Programmer's Guide for information about RDD limitations.)
lAll
Type: Usual
A value of TRUE specifies a scope of all records.  Use FALSE if you want to indicate other record scoping conditions (that is, <nNext>, <nRecord>, or <lRest>).  The default is FALSE.
cbWhileCondition
Type: Usual
A code block that defines another condition that each record must meet in order to be processed.   As soon as a record is encountered that causes the condition to fail, the operation terminates.
If no scope is specified, <cbWhileCondition> changes the default scope to <lRest>.
You define the scope using one of these three, mutually exclusive arguments.  The default is all records.
cbEval
Type: Usual
A code block that is evaluated at intervals specified by <nInterval>.  This is useful in producing a status bar or odometer that monitors the ordering progress.  The return value of <cbEval> must be a logical value.  If <cbEval> returns FALSE, indexing halts.  The default is NIL.
nInterval
Type: Usual
A numeric expression that determines the number of times <cbEval> is evaluated.  This argument offers a performance enhancement by evaluating the condition at intervals instead of for every record processed.  To step through every record, you can specify a value of 0.  The default is 0.
nStart
Type: Usual
The starting record number.  To start at the beginning of the file, specify a value of 0.  The default is 0.
You define the scope using one of these three, mutually exclusive arguments (use 0 or FALSE for the others).  The default is all records.  Record scoping information is used only to create the order.  It is not stored in the index file and not used for index updates and reindexing purposes.
nNext
Type: Usual
The number of records to process, starting at <nStart>.  Specify 0 to ignore this argument.
nRecord
Type: Usual
A single record number to process.  Specify 0 to ignore this argument.
lRest
Type: Usual
TRUE processes only records from <nStart> to the end of the file.  FALSE processes all records.
lDescend
Type: Usual
Specifies whether the keyed pairs be sorted in decreasing or increasing order of value.  TRUE results in descending order.  FALSE results in ascending order.  The default is FALSE.
lAdditive
Type: Usual
Specifies whether open orders should remain open while the new order is being created.  TRUE specifies that they should remain open.  FALSE specifies that all open orders should be closed.  The default is FALSE.
lCurrent
Type: Usual
Specifies whether only records in the controlling order — and within the current range as specified by OrdSetScope() — will be included in this order.  TRUE specifies that the controlling order and range should be used to limit the scope of the newly created order.  FALSE specifies that all records in the database file are included in the order.  The default is FALSE.
lCustom
Type: Usual
Specifies whether the new order will be a custom built order (for RDDs that this feature).  TRUE specifies that a custom built order will be created.  A custom built order is initially empty, giving you complete control over order maintenance.  The system does not automatically add and delete keys from a custom built order.  Instead, you explicitly add and delete keys using OrdKeyAdd() and OrdKeyDel().  FALSE specifies a standard, system-maintained order.  The default is FALSE.
lNoOptimize
Type: Usual
Specifies whether the FOR condition will be optimized (for RDDs that support this feature).  TRUE optimizes the FOR condition, and FALSE does not.  The default is FALSE.

Return Value

Type: Boolean
Remarks
This function is identical to DBSetOrderCondition(), which you can refer to for more information.
Examples