B
Bruce
I have been searching for some time now for a solution to
an old problem: The scroll wheel pages through records
rather than moving around within the form. One solution
calls for the installation of a .dll file and a macro
pointing to it. This, however, is not an option, as it
involves modifying dozens of workstations, and would need
to be performed every time a new computer is set up.
Setting Cycle to Current Record or Current Page
accomplishes nothing. If I set Allow Additions to No it
disables the scroll wheel, but then how do I add a
record? I cannot expect users to remember that their
scroll wheel works differently in Access than in any other
situation. Somebody will inevitably change the wrong
record (maybe it will be me).
It is necessary that users be able to modify records other
than the current one. They might need to go back a dozen
records. Any ideas or suggestions? Again, the .dll
solution is not practical. The second solution in the KB
article would actually work better, I think, since nobody
is likely to be opening the VB editor from within the
database in question, but I do not know enough about VB to
say for sure.
I welcome any suggestions.
an old problem: The scroll wheel pages through records
rather than moving around within the form. One solution
calls for the installation of a .dll file and a macro
pointing to it. This, however, is not an option, as it
involves modifying dozens of workstations, and would need
to be performed every time a new computer is set up.
Setting Cycle to Current Record or Current Page
accomplishes nothing. If I set Allow Additions to No it
disables the scroll wheel, but then how do I add a
record? I cannot expect users to remember that their
scroll wheel works differently in Access than in any other
situation. Somebody will inevitably change the wrong
record (maybe it will be me).
It is necessary that users be able to modify records other
than the current one. They might need to go back a dozen
records. Any ideas or suggestions? Again, the .dll
solution is not practical. The second solution in the KB
article would actually work better, I think, since nobody
is likely to be opening the VB editor from within the
database in question, but I do not know enough about VB to
say for sure.
I welcome any suggestions.