>>>Ok. It's not really a question.. it's rather something I found out while debugging... When you look at the MSDN library, it tells you that the WHEN event happend as soon as you try to get the focus, and then the gotfocus event happen.. But according to what I just experienced, THIS IS WRONG, at least for the buttons I was using. It seem that the gotfocus event happen first, then the click, AND THEN the When event..
>>
>>Works as advertised for me. But the When() is firing again after the Click.
>
>Well, that was my problem.. I didn't want anything to happen after the click...
>Maybe it actually happen before also, but the fact that it happend adter is bad.. relly bad for me, so I used the gotfocus instead, which hapen right before the click anyway

That's because the button regains the focus after the click, therefore it checks if it can do it, and that's where .when jumps in. You could SetFocus() to something else in your .click and the .when shouldn't fire again.