>>
>>In VFP 9 they can be used:
>>

>>CLEAR
>>SET DELETED ON
>>CREATE CURSOR Test (TBL_ID_FLD C(20),TBL_INT_FLD int)
>>INDEX ON TBL_ID_FLD + BINTOC(TBL_INT_FLD) FOR NOT DELETED() TAG Test
>>SYS(3054,12)
>>SELECT * FROM Test;
>>WHERE TBL_ID_FLD + BINTOC(TBL_INT_FLD) LIKE 'asdasdasda%' INTO CURSOR crsTest    && Full
>>?
>>SELECT * FROM Test;
>>WHERE TBL_ID_FLD + BINTOC(TBL_INT_FLD) = 'asdasdasda' INTO CURSOR crsTest        && Full
>>SYS(3054,12)
>>

>
>You see, in my case most queries would be like this:
>
>

>SELECT * FROM Test;
>WHERE TBL_ID_FLD = 'adadfasd' and TBL_INT_FLD = 2 INTO CURSOR crsTest        && Partial
>SYS(3054,12)
>

>
>Does Partial mean that the Rushmore will only use the TBL_ID_FLD portion of the index tag?

Rushmore will only use the left part of a comparison (or of a partial comparison, in the case of AND), if it exactly matches the index expression. So in this case, for optimization, you should have separate indices on TBL_ID_FLD and TBL_INT_FLD.

Unless here, too, there are new features in VFP 9 I am not aware of (sigh).