>They aren't, by any chance, typing in a space somewhere? Have you seen them do this, or have you yourself been able to do it? Since it can be picked from the list, I'd be suspicious that what the user *thinks* they are typing isn't what's in the list.
>
>For example, it's hard for users to understand why

" There is a space at the beginning" and "There is a space at the beginning"

are not the same.

This would be a good thing to investigate if the combolist style prop = 0, but in fact it = 2. So only list members are accepted by VFP's interactive search.(...he said, naively....)

Furthermore, when the problem occurs, all of the textfield controls that have a record field as a controlsource, except one, have a value that is consistent with the key value (also a field of selected row).

I have set up a trap that triggers when the displayed value of the control (which I presume is stored in control.value) is not equal to its controlsource.
I cannot imagine why this should ever happen in a simple textbox, but its the only thing I can think of to try to flush out this elusive bug.

One other clue could be that I do not refresh in the combolist's valid. Only in it's interactivechange. I've gotten a little hinky about refreshing in the valid of a combolist after some of the stuff I've read. Again, everything does appear to be refreshed at the right times, except the one field, when this problem occurs, so it's hard to believe lack of refresh is a source of the problem.

I'm thinking some kind of server delay/buffering interface/race condition weirdness could be at fault...explaining why selecting from the combo's dropdown list (rather than using the interactivesearch) clears the problem.