>VFP 9 introduced the new BINARY index option. In reading the online help, I noticed that BINARY indexes can not (among other limitations) be used for SEEK's.
>
>I assume BINARY indexes can be safely used in SQL SELECT WHERE or HAVING clauses but NOT in SQL SELECT GROUP BY or ORDER clauses. Does this seem like a valid assumption?
>
>

>SELECT ... WHERE MyBinaryIndexField = somevalue
>

>
>Is there a best practice list of scenarios where BINARY indexes make sense?
>
>Thank you,
>Malcolm

The binary is for functions returning .T. or .F., for instance DELETED(), ISNULL() or EMPTY(). With these binary indexes (indeces ?), VFP will load these index bitmaps into memory whenever needed, and since these binary bitmaps are much smaller than ordinary index bitmaps, the response will be much quicker. These new binary indexes will be used in Select * Where xx, Browse For xx and similar situations.