Combobox text display error

[Hoop]

Anyone come across this? With capslock on, typing into a combobox after a few
letters are typed in, the text in the combobox fleshes itself out, but not in
the normal way.

The normal way is for Access to display in the combobox the first entry in
the list that starts with the letters typed in by the user eg type in "ha"
and the text in the combo box might display "Hackett Craig" if that is the
first entry in the list that begins with the letters "ha".

But what's happening in this situation is after "ha" is typed in, the "w" is
typed in (so the first 3 letters typed in are now "haw", the text displayed
in the combobox is "HaWckett Craig" - and there is no such name in the combo
box list.

However, there ARE names in the list beginning with "haw" but these are not
automatically displaying, which you would expect them to. Wierd.

 

[pemigh]

Anyone come across this? With capslock on, typing into a combobox after a few
letters are typed in, the text in the combobox fleshes itself out, but not in
the normal way.

The normal way is for Access to display in the combobox the first entry in
the list that starts with the letters typed in by the user eg type in "ha"
and the text in the combo box might display "Hackett Craig" if that is the
first entry in the list that begins with the letters "ha".

But what's happening in this situation is after "ha" is typed in, the "w" is
typed in (so the first 3 letters typed in are now "haw", the text displayed
in the combobox is "HaWckett Craig" - and there is no such name in the combo
box list.

However, there ARE names in the list beginning with "haw" but these are not
automatically displaying, which you would expect them to. Wierd.

 

[pemigh]

The solution (just discovered after years of aggravation!): Change the combo box's "Allow Autocorrect" property to NO. That property is listed under "Other".

pemigh

 

[Access Developer]

Those of us who've been around the product for a long time tend to call that
feature "Autocorrupt" and advise, unless you feel a compelling need, to turn
it off for every database. Though I don't have any "inside information" on
design decisions made by the Access team, I suspect it's one of those
"flashes of brilliance" by someone in the design team that was implemented
and actually used by enough "enterprise-level" customers that Microsoft
decided not to take it out even though it is, more often, a PITA than a
help.