We have indexes on our views that we don't create until the user wants to
sort (e.g., by double clicking a grid header)
It takes a split second longer to create the index than change the SET
ORDER TO an index that's already created and the records stay in the index
order, whereas the ORDER BY clause only orders when the SELECT fires.
Either is faster than requerying the view...
I would recommend going ahead and indexing them.
-- For legit e-mail, remove underscores
> Is there a way to change the order of the records in a local view
> without destroying and re-creating the view in the database (VFP 5.0a)?
> I don't want to create indexes each time I open the view since that will
> take a long time as the number of records in the view increase. As far
> as I know, the parameters in the view can only be used in the WHERE
> clause. Any suggestions?