>>>Try setting _DBLCLICK to 1.5 or 2 in your form
>>
>>
>>What does this have to do with the incremental search issue????
>
>The user has to type as fast as the Win95 double-click speed for the Incremental Search to perform correctly. By slowing this down by changing the _DblClick property the Incremental Search works for slow typists (or, of course, fast mousers)
>
>Usually you increase the _DblClick value in the WHEN code and return it to its default setting in the LostFocus so there is as little impact on OTHER programs as possible.
>
>The link between the Inc.Search and the DoubleClick speed is a real oversight in my opinion.

Hi Barbara -

I've seen so many questions on why incremental search doesn't work, I think this is worth an entry in the FAQ section. I just went to look and couldn't find anything. Until I started seeing references to the _dblclick connection on the UT, I thought VFP had a different definition of incremental search than I! (I had gone the interactivechange and keypress event route to get incremental search combos to work.) But after seeing the connection, I went back to some combos which weren't working and typed really fast. Only then did the incremental search work. But if I typed at a more leisurely pace (e.g. without caffeine;), no go. The alternative is to include a tool tips message to users to 'peddle faster':)

Sylvia