David,

I saw this the other night, but didn't have any idea. I've never had a cbo act up on me and my cbo class has had the _dblclick set/reset code in it since day one.

I couldn't really follow your sequence or exactly when the value is changing on you. I put two VFP6+SP3 baseclass cbo's on a form, both had _dblclick=1 in GotFocus and _dblclick=0.5 in LostFocus. I set RowSource=a,ad,ada,adam,adams,b,be,bev,m,mi,mic,mik,mo, RowSourceType=1, Style=2

Both cbos work the exact same from my testing. I can click to drop the list and type and the incremental search works. Wait more than 1 second and a new search will start. Typing without dropping the list works too. Note though if you quickly type a-d-a wait a while and type another a it doesn't go back to the top it goes to adam I think this is the defined behavior of incremental search. Because it seeks from the current item value.

If you can create some simple form that illustrates the problem and use the ClassBrowser to dump out the code and post it maybe we can isolate the problem and find a workaround. If it really is a bug in VFP we can get it to MS.

>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.
...