>Hi all,
>
>A user emailed today to say that they would like me to "fix" something that happens in a combo box - combo box that gets its rowsource from a small array (5 rows) bound to a view.
>
>The list has 3 rows in it that all start with "T" - these users are very keyboard centric as they like to move through the fields quickly for quotes. When they get to the combo box, some have figured out that if they press the "T" one, two or three times, they can get the choice they want. But they said it often "does not work" i.e. it does not cycle to the next item that begins with a "T".
>
>Checking the code, there is not much that fires off of the methods - but if try testing it by changing how fast I hit the T, it can cause it to "fail". That is, if I leave approximately 1/2 a second between key taps, it works as expected. If I hit it much faster, it then fails.
>
>I could not see any property that controls how fast VFP processes keystrokes - is there some other setting?

As Naomi said, _INCSEEK controls this. To apply it only to the combo, you could change it in GotFocus and reset it in LostFocus.

Alternatively, teach your users that they can actually narrow things down by typing more than one letter of the item they want. So if your three T's are Terry, Tom and Tyrone, the fastest way to Tyrone is to type Ty.

Tamar