Optimizable Expressions:

  An optimizable expression is any expression found within the FOR clause 
  of a supported command/function that takes on the following form: 

      < index key > < relational operator > < constant value >

  An < index key > may be any key of the open indexes in the currently 
  selected work area.  Valid relational operators are "=, ==, !=, #, <>, 
  <, >, <=, >=, $".  The < constant value > may be any expression that 
  evaluates to a constant value.  This includes literal values such as 
  "100.00", or any memory variable, field, or user defined function. 

  Multiple optimizable expressions may be joined with the .AND. and .OR.
  logical operators to form complex optimizable expressions.  It is not
  necessary for all expressions in the FOR clause be an index key.  Non-
  indexed expressions can still be optimized through partial optimization.

  EXAMPLES:

  If the following indexes or tags (CDX files), with the respective index
  keys, were active...

      INDEX or TAG          INDEX KEY
      ------------          ---------
      SALARY                Salary
      NAME                  Last+First
      DATE                  Date
      STATE                 State

  ...then the following would be fully optimizable expressions:

    .  Salary > 25000 .AND. Salary < 30000

    .  Last = "Hewson"

    .  Salary > 25000 .AND. Last = "A" .AND. State = "CA"

  Expressions that contain at least one indexed expression are still
  optimized via partial optimization.  Note the non-indexed fields.

    .  State = "FL" .AND. Age = 21

    .  Salary > 25000 .AND. Last = "A" .AND. State = "CA" .AND. Zip = "92656"

  The following are the instances when optimization will not be available.

     . No database in use.
     . Not a SIx Driver workarea.
     . No index(es) in use.
     . Database contains over 524 million records.
     . No matching index keys found.
     . Not enough memory.
     . FILTER/FOR condition contains LOCAL or STATIC variables.
     . Not a logical condition.
     . FILTER/FOR condition contains an extended expression.
     . Matching key found, but in RYO, UNIQUE, or CONDITIONAL
           index that the order is not currently set to.