>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 was afraid you were gonna say that.

>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


Yeah. I had trouble describing the problem succintly. Here's another attempt.
(I use VFP6/SP3)

combo1 selects work order records and combo2 selects values from a lookup table and puts them into a field of the selected work order. The field of interest is the controlsource of combo2. Both combos set _dblclick to 1 sec in gotfocus and return it to its default value (333 msecs?) in lostfocus

select a record with combo1 then use combo2 to scroll to value x, thereby setting the corresponding field of the selected record.

now select a different record with combo1 and note that the value of the field of interest (in combo2) is (say), y.

now click on the dropdown button of combo2 (do not scroll...just click to drop down the list). Immediatly, combo2.value changes to x and the field (which is the controlsource) is changed to x also.

If after selecting the second record, I move to combo2 and open it without using the mouse (tab,tab,tab...spacebar), the problem does not occur and then subsequent clicking on combo2 doesn't do anything.

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

I will try to create this with a simple form in the next couple of days.

In the meantime, do you see any problem if I lengthen _dblclick in the click of the combo? I really do need to slow down the interactive search timeout.