>Hi, Mike
>
>Yes, I've tried limiting the results to 500. Actually, the stats I listed originally (something like 30 seconds) was with this limit in place. Without the limit, the 12,000 records takes some 2+ minutes!
>You're right, though: users should not have to view such a large selection. This could be the key in this type of task. Unfortunately, I have other apps that users do want to scroll through all records (no matter how large), I suppose to get a feel for trends or such. So I may have to approach this problem later, anyway.
>Mark
>
>>The Advanced Options menu in the View Designer has an area that allows you to limit the size of your result set to a specific number of MAX RECORDS. You could create a parameterized remote view as show earlier then check _TALLY for the number of matches. If this equalled your predetermined MAX RECORDS, alert the user to be more specific and reissue the query.
>>
>>If your users are at all like mine, I am sure they would not want to scroll through a list of over a hundred or so names.

I've got systems that have over 1 million records and a web interface. I deal with this problem by first doing a count of the matches and returning that so they will know to refine the search. I also limit the total I'll return over the web to 250, then you can do a next/previous thing if you have to.