Re: Control Exit event kills Button Click Event in Access2002 Form
From: Dirk Goldgar (dg_at_NOdataSPAMgnostics.com)
Date: 10/20/04
- Next message: Don: "Cursor to the end!!!"
- Previous message: Don: "Row Height Question"
- In reply to: Mike Elliott: "Re: Control Exit event kills Button Click Event in Access2002 Form"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 20 Oct 2004 12:08:50 -0400
"Mike Elliott" <Mike Elliott@discussions.microsoft.com> wrote in
message news:D1B77F35-2113-4C28-94EB-390083A1F609@microsoft.com
> I left out an important detail. The Exit procedure determines which
> field to move to next. The DoCmd.GotoControl statement in the Exit
> procedure moves the focus to a third control.
>
> This causes a problem because users have to Click the button multiple
> times. Each click fires the "Exit" Event for whichever control has
> the focus. When they get to a control with no Exit event, then the
> Click event for the button will fire.
That makes sense. The focus has to get to the button before it can
receive the mouse click, and you're preventing it from getting there.
If you need to find a way to work around this, I'd guess you need to
move the focus-shifting code out of the Exit event of that control, and
put it either in the button itself (if that makes sense in the context
of what you're trying to do), or in the GotFocus or Enter event of a
control that you place next in the tab order. But the specifics will
depend on what you're trying to do.
Good luck.
-- Dirk Goldgar, MS Access MVP www.datagnostics.com (please reply to the newsgroup)
- Next message: Don: "Cursor to the end!!!"
- Previous message: Don: "Row Height Question"
- In reply to: Mike Elliott: "Re: Control Exit event kills Button Click Event in Access2002 Form"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
