>>I don't follow you here, do I set the order on or off. What does Rushmore need exactly.
>>
>>Bear in mind, on an XP platform none of this is necessary???
>in order to speed things up in rushmore it needs an index on every parameter of the where clause
>
>if query like that
>
>select * from myfile where upper(myfield) = [FRANK]
>
>you need in index on upper(myfield)
>then rushmore can optimize the query. don't set any order just have the index on the field.
>the index has to match the left side of your where clause phrase
>
>search for rushmore in the help file to see more

Actually Peter, in a SQL command, the current order is reset as the table is re-opened with a new alias. The order affects adversely affects SET FILTER.