Setting _dblclick caused my combolists to behave badly! In a nutshell, clicking on the dropdown button for a combolist would cause it to revert to a previously selected value even though none of the observable state variables (controlsource, value, displayvalue, list[],listitem[]) still contained the previous value.

Here was the problem:

I have two cbolists. The main one, not tied to any controlsource, selects work orders, by number, from a table. The secondary one is controlsourced to the .opcode (out of house processing code), a field of each work order.

Nominally, everything works fine, but the following sequence causes badness.

(gotfocus of the opcode cbo sets _dblclick to 1 sec and lostfocus restores its value)

select w/o x
select opcode = n from opcode dropdown list

select w/o y
note that its related opcode value = m

now click on opcode dropdown button (just click, don't scroll or
do anything else). Note that the opcode reverts to n. This is, at least, very inconvenient and frankly, I think it is evil.

Interestingly, tabbing to the dropdown list and opening it with say, the space bar, does not cause the field to revert to n.

This behavior had me very perplexed and after several days of banging, a little angry. I was able to determine that the reversion was occuring in some hidden corner of the combo where I couldn't trap it. (Hiding during development is evil, he said, heretically).

It probably should have occured to me sooner to at least test removing the alteration of _dblclick. When I did, the problem disappeared.

Looking at some of the other recent messages where _dblclick is discussed, I see that increasing its value in the gotfocus is the accepted practice. So how come nobody else has experienced this strange, and evil side effect?

Am I the only person who thinks messing with the _dblclick value to effect keyboard interpretation is like using a screwdriver for a chisel? (Hmmm. Let me guess. The keyboard timing used by interactive search is deeply embedded in some hidden corner of an object and screwing with _dblclick was a hack to effect a change from the outside).

Sorry if I seem a little sarcastic about the hidden world of OOPdom tonight. I guess I'm just one of those ol' dinosaurs who still believes that mostly, darkness just helps evil make a living.

Bottom line of all of this is I don't know how to slowdown the interactive search key response to a resonable value without having this bad side effect.