Disable mousewheel

[de muur]

It is standard In Access forms that when using the mousewheel you will scroll
to the next or previous record. I don't want that in my application. Does
anyone knows a solution?

Klaas Muurling
Leiden
Holland

 

[BeWyched]

I don't know the answer to this and would welcome a solution! As a fix I've
changed the form so that it stands-alone - i.e. its Record Source is blank so
it is detached from the underlying table. I then load the data from the table
using the form's 'On Load' event.

Its a bit cumbersome but as the form isn't attached to a table, scrolling
using the mouse wheel has no effect.

Not a good solution but, maybe, a way forward for you.

 

[Rick Brandt]

It is standard In Access forms that when using the mousewheel you
will scroll to the next or previous record. I don't want that in my
application. Does anyone knows a solution?

Klaas Muurling
Leiden
Holland

I use this solution...

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

 

[de muur]

Thise is the solution I use when I work with an Oracle or SQLserver database.
But in this application I use an Access back-end because the develop-time is
very important. It's quicker to use all the standard Access facilities with
forms etc. But I don's want to scroll with the mousewheel to another record!

 

[de muur]

Great, it works.

Thank you Rick!

I use this solution...

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

 

[Tim Ferguson]

It is standard In Access forms that when using the mousewheel you will
scroll to the next or previous record. I don't want that in my
application. Does anyone knows a solution?

Better than killing the wheel is avoiding the problem altogether. It's
kinder on the network, kinder to other users of the database, and less
interfering for your user to base the form on just one record at a time.

Instead of using a Form.Recordset like "MyTable", base it on a query like
"SELECT * FROM MyTable WHERE MyPrimaryKey = 2988". You can reassign the
identifier from within the form itself, as long as you call the Me.Requery
method afterwards. This absolutely prevents the user editing the wrong
record, because she only has access to one at a time.

Hope that helps


Tim F