More info which may help with this - no matter how fast I type, it always takes at least .5 secs to return to the forms keypress event, which seems to explain where the delay is. How can I get rid of this .5 second delay? Over 10 characters, that means the user has to wait 5 seconds, which is way too slow when entering hundreds of pieces of data.

>I've created a custom incremental search which I use on a grid. I intercept keystrokes at the form level and build a string, which I then use to seek the table to which the grid is bound. I use a timer to reset the string if 1.5 seconds of inactivity occur.
>
>It works OK until I hit a space, at which point it slows down considerably (about a 1-2 second delay). I've tried creating an index with no spaces and ignoring when the user hits spacebar, which does not help. As far as I can tell, my index is Rushmore optimized: upper(vname).
>
>I've also timed each step in my keypress code, and none of them even register except the seek, and it usually takes less than 0.1 seconds, including when I hit the space.
>
>I don't want to use a listbox because of the space issue, which does not work with the built in incremental search. I know Tamar Granor did a piece on QuickFill in listboxes in the Sept. 98 FP Advisor, which I no longer have.
>
>Any ideas on how to speed this up, or on how to use a listbox and have it include the spaces in the incremental search?
>
>Thanks,
>
>David