Stop records from changing when using a scroll mouse on a form

[BZeyger]

I have a form that contains numerious text fields from a table. When I scroll
the mouse wheel, the records change. Is there a way to turn off this option?

 

[Beetle]

See this link;

http://www.lebans.com/mousewheelonoff.htm

 

[Douglas J. Steele]

Check what Stephen Lebans has at http://www.lebans.com/mousewheelonoff.htm

 

[BZeyger]

Is there anything for access 2003 or anything without having to download a
file?

 

[Beetle]

Not that I'm aware of.

 

[Larry Kahm]

Doug,

I thought the form's Cycle property, when set to "Current Record," would
prevent the wheel from shifting off the current record. Is that not the
case?

Larry

 

[Douglas J. Steele]

I don't believe so. See, for example, http://support.microsoft.com/kb/278379
While that only mentions Access 2000, it was the same for all versions up to
(and including) Access 2003. It's only in Access 2007 that the default
behaviour has been changed.

 

[Allison Wonderland]

I found a limited solution. In my databases I typically have one form that
displays a list of records and then users doubleclick on the one they want to
open. That in turn opens a detailed form that is filtered to that one record
only. Even then we were having a problem with the mousewheel causing the
form to go to a new record. We thought we could fix that by setting the
AllowAdditions property to No, but for some reason when you have a filter
applied, Access ignores the AllowAdditions property and allows them anyway.
What finally did work was this bit of code in the OnCurrent event:

DoCmd.GoToRecord acActiveDataObject, "YourFormNameHere", acFirst

Essentially what happens is when someone goes to use the scrollwheel to
scroll down, it immediately puts you back to the first (and only) record.
Scrolling up doesn't have any effect anyway when there's just one record.
The record will update when the user tries to scroll so if you have any code
that runs on an update event or a dirty event, this may not work for you, but
I've found it works well for me in most cases.

David Allison