>>But MouseUp fires,...
If only! I put wait window code in click, mouseup and others and the same pattern holds,i.e., the selection always changes, but mouseup, click and interactivechange don't always fire until "touched" a second time. It's as if the event is interupted and is ready to go when clicked on again. Of course, that's exactly when the InteactiveChange shouldn't fire because nothing is changing at that point, the item has already been selected.

I might try to create a class and bind it to the listbox and see if it can 'hear' the event somehow.

Gary


>>I have InteractiveChange code in a listbox to refresh some form controls based on the selected item. It works *most* of the time but not always. I click on an item in the listbox and the selection changes as it should, but the InteraciveChange event may or may not fire.
>>
>>If the event fails to fire, I can click on the selected item again and the event fires. How can the selection change and not fire the InteractiveChange? Thanks for any insights.
>>
>>Gary
>
>One "for sure" way to cause this is with a mouse drag. Press the mouse button down and hold it down on one item in a list, drag to another item in the list and release the mouse button. SelectedItem, etc., are all updated just like you'd expect but InteractiveChange() doesn't fire even though there's a change and it was certainly interactive. <g>
>
>Click won't fire because of the drag. so at least there's a way to work around it.
>
>This goes back as far as VFP6, if memory serves. It has been reported.