>Hi all,
>
>I have a number of tables that has information about applications (people applying to receive benefits from a program).
>
>I will be using a view (or mulitple views) to display the data in a grid. I want to give my users the options of displaying:
> - all applications
> - completed applications
> - incomplete applications
>
>What is the best way to handle this? once the size of the data gets large, Filter's are not efficient, right? I could have 3 different views and change the RecordSource for each.
>
>I've thought about somehow having a view parameter that will collect the entries required, but don't quite know how to handle this. If the main table has a field, lCompleted, obviously, I can query for all completed applications or all uncompleted applications, w/something like:
>
>... WHERE lCompleted = ?Thisform.lShowCompleted
>
>But how to expand that to query for all applications? this might be totally obvious, but I can't see it.

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.