>>If the table scanned is sorted by an index are you saying that scan might not go in the sorted order?
>
>Exactly.
>
>This happened to me - but now that you ask, I think it was rather with a REPLACE ALL command.
>
>But a quick test confirms that the same happens with SCAN/ENDSCAN, too. It seems the records are processed in the order of recno().
Sorry - I just realize that I had set up the test incorrectly. It seems the records are processed in the correct order after all - in the case of scan/endscan. I wouldn't count on this always being so, though.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
