Milt,

>Please let me know if this would be a good idea in reference to tables and views. I have a table with about 100,000 records and potentially more containing information about subscribers. These subscriber subscribe thru one of three cities. I need to create a lookup screen that has three option button one for each city. When the user click the city button the lookup grid refreshes. I tried both using a view and a filter and found that you are correct in the fact that in the case views are slower. After the user locate the correct subscriber I need to pull in from multiple table information regarding that subscriber. So in this case the result set would be small. Would this be a good use for a view. Please let me know what your ideas are about this.

It seems that you'll need filters for the lookup table since it's going to be rather large and selectivity is low (resultset is about 33% of the entire table). An advantage is here that you can use the original indexes to perform a incremental search (highly recommended in your case, for examples of an incremental grid, see files section) and you'll not loose time executing the query of the local view.

The detailed information about the select desciber could be a view because the selectivity is high (detail information of 1 of 100.000 subscribers), so will probably not lose much time executing the query.

Good luck,

Walter,