Thanks for the advice re: Docmd, and the new code for
setting the focus the way I wish. I've tested it, and it
not only works, but feels right. Normally, my users will
be entering multiple records in the detail subforms, but
when they're done, they can keep in rhythm and simply hit
<Tab> or <Enter> to go on to the next.
Obviously, if they want to go back to the main form or
skip to a different subform from where they are, they can
still use <Ctrl>-<Tab> and <Ctrl>-<Shft>-<Tab>, so I will
teach them this. But for grunt data entry, this method
makes a smooth flow that I think they will appreciate.
Thanks for your help in getting it implemented.
Best regards.
Kevin Sprinkel
Becker & Frondorf
I know what you mean about it not being intuitive
but . . . in my experience, users who can't go beyond the
intuitive keyboard actions also tend to use the mouse for
form navigation, no matter what I do or tell them (it
drives me crazy sometimes)!
First, I would avoid the Docmd.Gotocontrol method - I do
not like docmd.methods for form navigation because they
aren't as robust as the form and control methods that do
the same things (Setfocus for example).
If I understand you correctly you want to go from the
first subform to the first control on the second subform.
To do this, you first have to setfocus to the second
subform control, then to the control on the second subform.
For example - this code in the Exit event of the Custid
field on 'sfrm1' will move focus to the Custid field
on 'sfrm2'. The code is in sfrm1's class module.
Also, 'sfrm1' and 'sfrm2' are the names of the subform
controls on the main form (was not actually relevant in
this example except that it is