Any way to disable the mousewheel from moving to the next record (Access XP)

[Gijs Beukenoot]

Well, the question is all in the header, is there ?

I have a bound form that jumps around the recordset if the user uses
the mousewheel. Worse, if the user accidentally hits the wheel while
moving to another tab or subform or control (not everybody knows how to
handle Windows applications with the TAB and/or ENTER key), the user
ends up editing a completely different record...
I could implement a filter (or where) so only one record is shown but
that would limit the use of certain forms where I have a next and
previous button (among first and last and some others).
I don't see any possibilities (in Access XP) to disable the mousewheel;
I can't use a cancelevent (well, I can use it but it doesn't prevent
moving to a new record) and the only thing I can come up with is
setting up some code on the Current and Dirty and MouseWheel and
BeforeUpdate that, all together, will keep the user on the same record.

Any other thoughts?

Thx,

GB

 

[martialarts25]

I have the same problem in Access 2002 on Windows 2000. Have you had any
luck since posting this message? Do you have any work arounds? It seems
that it would be a simple fix but have not had any luck so far.

Thank You
martialarts25

 

[Dirk Goldgar]

Well, the question is all in the header, is there ?

I have a bound form that jumps around the recordset if the user uses
the mousewheel. Worse, if the user accidentally hits the wheel while
moving to another tab or subform or control (not everybody knows how
to handle Windows applications with the TAB and/or ENTER key), the
user ends up editing a completely different record...
I could implement a filter (or where) so only one record is shown but
that would limit the use of certain forms where I have a next and
previous button (among first and last and some others).
I don't see any possibilities (in Access XP) to disable the
mousewheel; I can't use a cancelevent (well, I can use it but it
doesn't prevent moving to a new record) and the only thing I can come
up with is setting up some code on the Current and Dirty and
MouseWheel and BeforeUpdate that, all together, will keep the user on
the same record.

Stephen Lebans has provided a solution:

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

 

[Gijs Beukenoot]

Dirk Goldgar formuleerde de vraag :

Stephen Lebans has provided a solution:

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

I'll have a look into that one, looks promising from what I've read on
the page.

Thanks!