>that's what i was afraid of. But how do i stop it. I might be able to trap the click event and just not do dodefault the first time the click is called.

Sounds like a reasonable thing to try, but it might be behavior you can't override without more work than it seems worth.

If you put code in the Click event to move focus to another object and back to the clicked one (with SetFocus calls or KEYB "{TAB}{Shift+TAB}"), that would do it, as long as it didn't fire a complex Valid event. A complex valid would make an unacceptable slow-down. And of course there's a problem (as my esteemed colleague Mr. Goff pointed out if they're doing intense keyboard data entry and you stuff the keyboard. Of course if they're clicking the mouse, they're not doing "heads-down" data entry.

Sorry I'm feeling long-winded today.