>Yes, Rushmore also applies to SQL. This thread was originally about SCAN WHILE vs. SCAN FOR and I sort of limited my explanation to that.

Late hours - I probably wasn't too clear, so I'll give it another shot. The docs ever since the advent of SQL in Fox state that having no order set will speed the queries. It's logical, ok. Now the question I raised is whether any plain xbase Rushmore optmizable command will run faster (with a Rushmore optimizable FOR expression) with order set to 0 than with active index tag. I just guessed that the speed difference shouldn't be dramatic, and thought you may shed some light on this issue.