if i may join this thread...
some of my users would sort of prefer not to have the effect(s) of using the
mouse to move from one record to the next, i.e. automatically saving any
changes made to a (sub)form, so this might be an ideal answer to the question
of how to get them to use the little arrows at the bottom of the screen and
to manually hit a 'save' button i placed on the same form.
what i did not understand from reading lebans blurb on his website was the
reference to "Bug Fixes" in the following blurb describing it:
"Please note this is an update from the March 09/04 release. Support has now
been added for Logitech Mice. The only difference between the feature set for
a MS Mouse and a Logitech Mouse is that you can scroll an open Combo control
from a MS Mouse only. Look at the code behind the sample Forms to see how to
turn the MouseWheel ON or Off. You need to import into your own MDB the
standard code module "modMouseHook" found in the sample MDB included in the
download zip file. Bug Fix for SubForms with ScrollBars. Bug fix for SubForms
without visible ScrollBars. Added support to specify an optional Global
versus thread specific hook to allow for multiple instances of Access."
perhaps i need a stronger pair of eyeglasses but i just did not find the
extra stuff i think he's telling me i need in addition to the mdb file!
lastly, entry to my users' app'n is governed by a mandatory
switchboard....would it be cool to put the mouse wheel 'on' and 'off' buttons
