Thanks for the info, Terry.

BTW, I know Joro Batista was asking about such functionality. May be he'll see this message.

I definitely would try this class in my fiture applications. And probably would use it in existing.

Thanks.

>I use inGrid now almost exclusively. I place it on one or more columns of a grid. When the user clicks on a column ingrid, through its properties selects the appropriate index and starts incrementally searching on that columns index. Be aware though if you use it on a form using the default data session and an already open table it can move the tables default index. Also, I modified it and added a incremental search speed property. I then normally put 5 in the property. The GotFocus method then sets the _DBLCLICK to 5 allowing the user time to type their search and go back and forward if needed. ie type NANCY oops typo backspace to NANC and add the E to NANCE. The LostFocus method then sets _DBLCLICK back to its default of .5 I love this component and so do my users. I came to the conclusion that ComboBoxes were only good for 20 or so choices. I now use a button, a fast find form, and a disabled txtBox for the results. This allows me to track things like hidden IDs
>with out messing up the users view of the data.
>
>Good luck
>Terry
>
>>Hi Cindy,
>>
>>>> Sorry for asking the basic, but how can we define the incremental search? Give me an example, please. I'm not 100% sure, that my understanding of it is correct.
>>>>
>>>
>>>PMFJI,
>>>
>>>An incremental search: If I were looking for your name among NANCE, NOBLE, NOSE, NOSONOVSKY, NOWHERE
>>>
>>>When I typed N it would move to NANCE
>>>When I typed O after the N it would move to NOBLE
>>>When I typed S after the NO it would move to NOSE
>>>When I typed N after the NOS it would move to NOSONOVSKY.
>>
>> Thanks for this explanation. Yes, my understanding was correct, I just was not sure :) Now the second question: It means, that InGrid should have only one column, right? Or it can work for several columns?
>>
>>TIA