scroll in mouse on a form

[00KobeBrian]

Hi,

How do I change the scroll action on a mouse when I open up an
Access form? Say instead of going to next record, it goes down the screen.
Please help. Thanks.

 

[Arvin Meyer [MVP]]

You can't change the action, but you can turn it off:

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

Also, there is an older program named FreeWheel that may offer some help:

http://www.geocities.com/SiliconValley/2060/freewheel.zip

 

[00KobeBrian]

So if this is used for multi-clients environment, I just need to put the dll
file to the same directory with the mdb and no need to put to the window
folder of every client machine and that should be fine, right? Thanks.

 

[00KobeBrian]

I just tried it out. I think I need to include the dll to the mdb because
when I run the mousewheelon, it gave me "function not defined...". But when
I do it through tool->references and then browse and after I click the dll
file, it gave me "can't add a refence to the specified file" message. Can
you please help? Thanks. I using Access97 and MouseWheelHook97.zip .

 

[Arvin Meyer [MVP]]

Hopefully, your database is split with a front-end on each workstation and
the data, if shared, on a server. You should not need to set a reference to
the dll, nor should you try to open the dll. Place a copy of the dll in the
same folder as your application's front-end. I'm not sure, but putting it in
the Windows\System32\ directory in addition or in place of the local folder,
should also work. When you open the form, put a boolean variable in the
form's declaration section and set the variable to MOUSEWHEELOFF in the form
open or load event.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

 

[Douglas J. Steele]

If you're in a multi-user environment, the application should be split into
a front-end (containing the queries, forms, reports, macros and modules),
linked to a back-end (containing the tables and relationships). Only the
back-end should be on the server: each user should have his/her own copy of
the front-end, preferably on his/her hard drive. The DLL would be placed in
the same folder as the front-end database. In other words, yes, you need to
copy it to each client machine.

--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)

 

[Douglas J. Steele]

There's code that you need to copy from the sample database into your
database. I don't have a copy of the database handy, but there's at least a
class module that has to be copied.

--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)