Stopping mouse wheel in Access 2003

[duncanjx]

Private Sub Form_Load()
' Turn the MouseWheel Off
Dim blRet As Boolean
' Call our MouseHook function in the MouseHook dll.
' Please note the Optional GlobalHook BOOLEAN parameter
' Several developers asked for the MouseHook to be able to work with
' multiple instances of Access. In order to accomodate this request I
' have modified the function to allow the caller to
' specify a thread specific(this current instance of Access only) or
' a global(all applications) MouseWheel Hook.
' Only use the GlobalHook if you will be running multiple instances of
Access!
blRet = MouseWheelOFF(False)
End Sub

I have tried loading this code as an event on the OnLoad event on a
form to stop the mouse wheel function but it is not working.
Any suggestions on what to do would be appreciated?

Cheers

 

[Rob Parker]

Did you put the main code for the MouseWheel function into a separate module
in your database? It needs more than just this code in a form.

Rob

 

[duncanjx]

Did you put the main code for the MouseWheel function into a separate module
in your database?  It needs more than just this code in a form.

Rob








- Show quoted text -

Hi
I just tried to add it to an event within the form for the OnLoad
event.
Duncan

 

[duncanjx]

Did you put the main code for the MouseWheel function into a separate module
in your database?  It needs more than just this code in a form.

Rob








- Show quoted text -

Hi Rob
I am using the datbase in a shared environment as well.
Some staff are accidently scrolling through some extra records.
Duncan

 

[Rob Parker]

Hi Duncan,

Did you put the accompanying .dll file in an appropriate folder on each
user's system?

Rob

Did you put the main code for the MouseWheel function into a separate
module
in your database? It needs more than just this code in a form.

Rob








- Show quoted text -

Hi Rob
I am using the datbase in a shared environment as well.
Some staff are accidently scrolling through some extra records.
Duncan

 

[duncanjx]

Hi Duncan,

Did you put the accompanying .dll file in an appropriate folder on each
user's system?

Rob





Hi Rob
I am using the datbase in a shared environment as well.
Some staff are accidently scrolling through some extra records.
Duncan- Hide quoted text -

- Show quoted text -

Hi Rob
Not sure how to set that up???????
Duncan

 

[Rob Parker]

Hi Duncan,

I'm afraid I can't give you a definitive answer for this.

If all your users are on a local network, and are in the same physical
location, you could simply go to each workstation and copy the .dll file to
an appropriate folder.

If that's not possible, and your application is already distributed to
users, you could send them the .dll file in a email and tell them where to
put it. This is a non-foolproof method, and the world is full of fools.

If you're distributing your application via some packaging method, then you
could include the .dll file in the package - probably with a
self-installation script. I've never done this, so can't offer any advice -
try searching this (or better, the microsoft.public.access.*) newsgroups, or
post a new question regarding this subject.

I was going to suggest that you trap the error that will arise from the
MouseWheelOFF call, and show a messagebox telling them how to fix the
problem, in their/your local environment, but my testing now shows that it's
a non-trappable compile error (Sub or Function undefined), and I don't know
how to detect that. Again, a new post with a different subject line (and not
in the .queries newsgroup) might be useful for you.

Sorry I can't help more,

Rob

Hi Duncan,

Did you put the accompanying .dll file in an appropriate folder on each
user's system?

Rob

<snip>

Hi Rob
Not sure how to set that up???????
Duncan