I'm creating a database that I am using as a testing program and I
would like the user to only be able to navigate records on a form
going forward. I was wondering if anyone knew of a way to do that?
Doing away with the navigation buttons is easy enough but I am also
wanting to do away with the mouse wheel function.

Any help you've got would be great, I've found almost no documentation
for mouse wheel functions.

Rob

Rob,
The easiest way to do this is to work with an unbound form that has a set of
custom navigation buttons coded by you. There are options on forms that get
rid of the built-in navigation buttons and scroll bars. Then you replace
them with some of your own. In my experience, though, data entry clerks
like being able to review and audit there work before it gets posted and
closed. For this reason I tend to attach my data entry forms to temp tables
and/or use the Data Entry mode of forms. In both cases once a clerk clicks
on a button labeled "Post" the new records are added to the back end systems
through my code, where I have a chance to run my own validation routines and
bounce anything that seems out of the ordinary or wrong. Assuming
everything goes according to plan my last step is to clear my temp table and
if necessary, add any records to be keyed on the next shift. This way a
failure in the process would still leave the previous shift's data entry in
my temp table where I can deal with it when I come to work.

"Rob" <google (AT) pinnaclepromos (DOT) com> wrote