>In my case, the 100,000 records are split over about 12-15 locations, so it would be reasonable as a first guess to assume that the view size would be on the order of 5,000-10,000 records (for a "main" office possibly quite a bit higher, perhaps 20-30K), so indexing on-the-fly could become a performance issue. Do you agree?
I am not sure - indexing should be fairly fast, I think; I am more worried about fetching the records for the view.
Speed tests are warranted.
Also, see if you can add a second criterion to reduce the result set even more. I mean, does the user really need to see 20,000 records at a time???
Depending on the data, you might specify a date range, for instance.
>BTW, I just read your FAQ on Rushmore. Very interesting.
Thanks.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
