>Hey Russell,
>
>>Let me make sure I understand. Are you saying that in a normal form - no calling of Click via DblClick - if the user double clicks an image (which is what the "button" is) the Click event fires as well as the DblClick? It that's true, I'd be surprised and would be unaware of that (up until now).
>
>Absolutley. Think about it. If you don't fire a click on a dblclick...when will the click fire? For every click you would have to wait to see if there was going to be a double click before firing the click.... that would be silly.

Yes, you're right. From a programming standpoint, you have one event - a double-click - and I'd only want one method firing, but there's really no way around it, as you've basically pointed out.