>>Also, on a funny note, as I was talking to Jean-René about, is to use the >filter for less than 3 characters and use the SQL for 3 characters and >more. At least, this is what we have found. Filtering on one or 2 >characters is immediate. After that, it starts slowing down. Workaround for >a bug with a funny coding. :) > >Oddly, I ended up with the 3-character limit myself on a half million >record table where the users were searching for all matches. It was a >compromise with the users wanting 2, but they didn't like the delay. Just crossed my mind - if the field we are filtering on is the current tag, we could just SEEK it and have it from the original table - no filter at all; should cover well for the one-two character case and supposedly fill up the visible part of the grid with records found (except for the impossible combinations like WZ, QH etc, where it would go EOF), and then for three or more do with a cursor.