Hi Terry,

How can we get rid of two white bars at the both sides on the InGrid? When I select a grid cell with a keyboard, there are 2 white bars. How can I avoid them?

Thanks in advance.

>Cool, I love this component and use it ALL the time.
>
>>Hi Terry,
>>
>>I finally understood, why my demo didn't work correctly. It depends on set exact settings. Our environment default is ON, so what's why it doesn't find the record. I will change KeySeek method like
>>
>>lcOldExact=set('exact')
>>***
>>set exact &lcOldExact
>>
>>I did some other changes also, for example, I don't want to change Header.Caption, so I comment these lines.
>>
>>I will also add a little code in the Init method to initialize cLocateExpression if it was not specified.
>>
>>So, I can modify my base grid class. I'll add 2 new properties:
>>lIncremental && logical property - if this Grid should use IncrementalSearch
>>
>>
>>lShowMemo - && logical property, if I need to show memo content in the grid or just 'Memo'
>>
>> And in FormatAndSetCaption method I will add code to handle this.
>>
>> Thanks for your advices.
>>>Most likely the inGrid index properties need to be setup. The column you put the ingrid component on (for this test) should be the index colunm of the table you are griding. So for example you have a name address table indexed by last name. Set the component on col1 - the last name column. The ingrid tries to use the current index by default without your intervension. Try this first. In the mean time I will try to snag an example form from my application here at Koinonia. It may take me an hour or so to extract one from the (fairly large) app I currently have. I will email it directly to you.
>>>
>>>Terry
>>>
>>>>Hi Terry,
>>>>
>>>> I've dowloaded the InGrid and I run the demo. It doesn't show anything :((
>>>>I type something, it shows, that I type, in the grid header, but it doesn't jump to the correct record :(
>>>>
>>>>What's wrong? Could it be the new version? Or do I do something wrong? May be you can send me your modified class to see, how it really works?
>>>>
>>>> Thanks in advance.
>>>>
>>>>>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