In any application that I build for non-Access-savvy users (and that's just
about everyone - except for my own databases), I don't use the standard
navigation buttons on single-record forms. I either use larger custom
buttons in the form's footer area (with code disabling those which are not
appropriate, such as Previous when they're at the start of the form's
recordset), or no buttons at all; the latter is generally the case on forms
which open to show details (normally via a details button or double-click on
a particular record in a continuous form).
In continuous forms, I'll usually only display record selectors if I'm
allowing users to delete records directly via the Delete key.
And finally, for most applications I remove all standard menus and toolbars,
and provide custom ones that only allow particular actions (generally a very
limited set).
HTH,
Rob
AccessMan said:
I really wasn't offended, since I unashamedly use the mouse wheel to great
personal advantage. Your point about a non-agile/non-alert user getting
into
trouble is certainly well taken. Whenever I train a new user, navigation
is
the most clumsy part, and I spend a lot of time imparting caution about
making changes to field data. I appreciate getting a feel for what others
typically do. Do you create big navigation buttons, or do you just use
the
ones at the bottom of the form?
<snip>
