
Signature
Trying To Feed The Hungry
> SteveM; Your suggestion seems to work. You have helped us feed the hungry
> and teach them how to prepare nutritious and healthy meals. We can keep
[quoted text clipped - 49 lines]
> > > Ex-Mainframer Learning Access To Help Feed
> > > the Hungry Through Harvesters Food Bank
> Another detail is to set all non-data controls to Tab Stop=no and Tab
> Index
> to progressively higher numbers. If not, it seems to interfere with
> stopping
> the Enter key from working normally and creating a record when not
> intended.
Keep in mind that you can also set the "enter" key as default key to fire a
button, and the "cancel" key (esc key) to cancel on a form.
If you look at the properties sheet for a command button, you see in the
other tab, a setting for
default
If you set default = yes, then when the person hits the enter key, that
button is fired. Thus, you should as a rule teach users to use the tab key
to move through the fields..and then you an make enter key hit you
close/save button.
Quite amazing that ms-access had this feature about 15 years before the web,
but if you look today, you see a lot of web based forms work with tab to
move tot he next field..and hitting enter = save/close.
in the "other" tab, right below "default" is a cancel setting, and if you
set that to "yes", then hitting esc key will fire the button...
So, try to use tab to move to the next...and save the enter key for when
done...you can thus have a new record appear during data entry without users
having to leave the keyboard. I sure with "old" mainframe experience, you
make that effort to allow users to not have to use the keyboard, or even use
the mouse to click on some save button...just have them use the enter
key..and then they get a new record.....

Signature
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com