Thanks Jim. I will try that today. Tinkering with the DODEFAULT()/NODEFAULT combination was the next thing on my list to try :-).

Bill

>Bill,
>
>here's an idea for your keypress code, tyr this and see if it helps;
>
> * Listbox Keypress
> DoDefault()
> * Now do you processing of the entries
>
> NODEFAULT && after you process your entries to keep the default keypress behavior from firing twice
>
>
>
>
>>>>I have a multi-select listbox on a form. As items are selected, I have to update a textbox on the form with amounts from the selected items. No problem with single items selected or multiple items selected with the mouse ( I use the mouseup event to process so the item is already marked as selected ).
>>>>
>>>>However, when the keyboard is used to select items, I use the keypress event to process in. But the item(s) is not marked as selected until after the event. I got around this with single items by processing the opposite of whether the item is currently selected. This won't work when multiple items are selected ( Shift + Space ) because the "in-between" items are not yet selected and I have no way of telling all the items that will wind up being selected after the event is completed. Is there another event I can use to do my processing in which the listbox "sees" the items as already selected?
>>>>
>>>>Thanks,
>>>>Bill
>>>
>>>Did you try count selected in InteractiveChange?
>>
>>Hi Edward,
>>
>>I looked at Interactivechange, but it fires whenever the pointer is moved, not just when items are selected. Valid only fires when Enter is pressed, not when items selected using Space bar. Will have to give it some more thought.
>>
>>Thanks,
>>Bill