>>>>but I my opinion Rushmore SHOULD be about using existing indexes to achieve the fastest query performance possible.
>>>
>>>
>>>>To ignore UNIQUE index tags is a waste and to be able to beat the performance of SQL by an order of magnitude
>>>>with old style xbase code is crazy.
>>>

>As for the use of UNIQUE indexes in Rushmore optimizations for SELECT-SQL: I see only one very special case when they could be used:
>
>SELECT TagExpr AS AField DISTINCT FROM ATable
>
>where the TagExpr is the expression of the UNIQUE index.
>
>I don't see any other case when they could be used for optimizations. Something similar goes for the indexes with a FOR clause.
>
>Am I right?
>
>Vlad

Yes, this is it exactly. I have a huge table and I just need a query of distinct TagExpr which returns a small number of records. I can use the COPY TO command which uses my UNIQUE index, however, I would have preferred that the SQL SELECT statement would have worked just as well.

Oh well, at least VFP always has many solutions to choose from.

Thanks to everyone for the input,