>Al,
>
>Thanks for your input.
>
>>Are you simply displaying data (i.e. not updating?) If so I'd be inclined to use straight SELECT - SQLs. You could use a combo or radio buttons for your main choices (All, Complete, Incomplete). You can also do neat stuff like put code in your grid header .Click() so the grid resorts based on that column - lets the user view by name, application amount, date, etc. You simply supply the correct ORDER BY clause.
>>
>>You need to remove the grid's RecordSource before regenerating the cursor, then restore it and the columns' ControlSources each time.
>
>Thanks...you must be reading my mind...I DO have radio buttons at the top of the form, and I DO use a grid where the user can click in the header to sort the data by various fields...but I usually use a view, creating the indexes on the view once, in the form LOAD.
>
>And, yes, in this case, I'm not updating the view...
>
>If using straight SELECT - SQLs, as you mentioned, I'd have to re-execute the SQL everytime the user wanted to sort on a different column? better to make a writable cursor and create all the tags once?
Sure, that's an excellent idea. You could use filtering expressions to implement your Complete, Incomplete etc. You'd need a total of 3 tags for each column you'd like to be able to sort by but that shouldn't be too hard to arrange.
INDEX ON Field1 TAG AllField1
INDEX ON Field1 TAG CompleteField1 FOR lComplete
INDEX ON Field1 TAG IncompleteField1 FOR NOT lComplete
...
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up