>>>The InGrid class does use the _DblClick variable in the KeyPress method. It uses this to "decide" how long to what between key strokes before starting a new search.
>>
>>I think, for VFP7 it should be _INCSEEK instead of _DBLCLICK.
>>
>>
>>>>Check out, if it uses _DblClick variable somewhere. It probably should be changed.
>>>>
>>>>
>>>>
>>>>>I'm using VFP 7.0 SP1
>>>>>I just tried hooking up the InGrid class that I downloaded from UT.
>>>>>Every time I try to use it, my computer locks up.
>>>>>
>>>>>I think I've traced it to the "set order to this.cOrderTag" in GOTFOCUS(). If I comment out that line (and the line in KEYSEEK()) and just use cSeekTag and set the display order in DE it doesn't lock up my computer, but then it freezes my keyboard after doing the seek in KEYSEEK(). Eventually it releases (about 10 seconds). It also freezes my keyboard if I use UPARROW or DNARROW. If I press UPARROW+DNARROW, it moves up 1 record then freezes for 10 seconds then moves down 1 record.
>>>>>The table I'm using only has 30,000 records in it.
>>>>>I've left cLocateExpression blank.
>>>>>
>>>>>TIA
>
>
>I think you're right buts it's coded for _DBLCLICK.

I'm using VFP6 so I'm not experiencing any problems. And I don't know what _INCSEEK is! However, it looks like the keypress method is using _dblclick to try to pace it's timing with the speed of your system.

Why don't you just try replacing with m.factored_dblclick = with a constant instead of _dblclick and see if it still has a problem? You would then know if it really is _dblclick or something else.