>This also seems to work. I didn't understand the active/close part you
>added? It doesn't seems to effect the speed so I could leave it out?

I just once had problems when I in a loop opened a cursor but forgot to
close it. If you get the right results without closing it explicitly, I can
see no reason for including this code (maybe ParamByName automatically
closes as well?).

>I changed my example to the zipcode, this seems to works even faster. It
>starts with number (our format is 1234 AA). I get almost instant response so
>I'am really happy with my incremental search on 500.000 records so far. But
>I still need to iron out some things like not start searching if keys are
>pressed very quickly. And the first search is still a bit slow.

You could try checking for IB_Query2.Fetching (I've never used this myself
though) The reason for your first search being slow is probably because it
has to prepare the statement (or did you mean whenever you typed one
character only?). You cannot avoid such a delay, but if you prepared the
statement upon starting your program maybe your users would feel more
comfortable with a "startup delay"?

Set