>The InteractiveChange fires for every keystroke in the drop down combo, the when only fires if an item has beconme selected.

This is not true from my experience.

Say a listbox contains two items, Jim and Erik, and its initial value is Erik. when I type a J (incrementalsearch = .T.), interactive change fires because the value changed. If I nect type an i (in quick succession) the value does not change, and interactivechange does not fire in the second keystroke.

>
>The When is not a legacy event, it does things and fires at times that no other event does.

This is why I was careful not to say it is a legacy event, only that I got into the habit of avoiding it because I have heard it called that. I do use it however for the purpose of deciding if a control should get focus.

>In fact it is THE event to react to a selection being made in a list or combo.

Still not convinced ... :-)

>The problem with InteractiveChange is that it fires too often and unless the code in it is really veryf ast, using it can slow the interface down quite a bit.

It seems to me this could be said about the when event, not the interactivechange event. If you want an event to react to a user selection, you might not necessarily want that event to fire when the user tabs through the control, which when does, and you might not want it to fire when the user expands the box to look at the choices but doesn't select anything, which when does.