>>Since Ed Pikman says it's often better performance, I'm sure it is!
>>
>To be precise I said nothing about better performance :). Probably, I said that it might be used for dynamic sorting, e.g. you brought up recordset to grid and want to give user the functionality to sort it differently. Obviously, it's not the best idea to recreate cursor/view many times with different ORDER by clauses, but it's faster to index view/cursor especially if it's small.

Sorry I misquoted you. Incidentally, I tried to use the idea today in an app I'm working on, where a view with an ORDER BY clause was coming up pretty slowly. Removing the ORDER BY and using INDEX ON fields TAG temp after opening the view did nothing to speed it up. (Just like you didn't say it would...)

Since I discovered by trial-and-error that you can include macro substitutions in views which you define programmatically, I think I'd use that approach to vary the ORDER BY clause in my views, where I have them, if they might change.

Thanks for your insight,
Rich.