Disable Mouse Wheel

M

Mark Schirle

According to Microsoft Article #308636 you can create a dll that will
disable the wheel.
I have followed there instructions very carefully but I am getting an
error when I try to load the form.
It says that it can't load the activex dll. Any ideas as to what is
going on here.
TIA
 
M

Mark Schirle

I found out you have to register the dll thru Access. You go to the
tools menu and then to ActiveX Controls and register it there.
I no longer get the error but it doesn't seem to do anything.
I'm trying to prevent the wheel from allowing the user to scroll to a new
record.
 
M

Mark Schirle

I'm aware of this method but I'm more interested in the Microsoft solution. I
want to know why this method is not working. Surely a MS MVP can respond with a
Microsoft solution.
TIA
 
N

Nick Coe \(UK\)

Mark said:
I'm aware of this method but I'm more interested in the
Microsoft
solution. I want to know why this method is not working.
Surely a MS
MVP can respond with a Microsoft solution.
TIA

MVP's are not Microsoft employee's. MVP is an award for
professional Access community service. They probably feel
constrained from saying you come across as a rude, thankless
smart ar@e, but I don't!

Steve Lebans cooked up the mousewheel hook because of
perceived shortcomings in other methods.

--
Nick Coe (UK)
AccHelp v1.01 Access Application Help File Builder
http://www.alphacos.co.uk/
Download Free Copy
----
 
K

Ken Snell [MVP]

Which is why I recommend Stephen Lebans' solution. It works without hassles.
 
M

Mark Schirle

Sorry I didn't mean to offend anyone. I didn't say there was anything wrong with
the Stephen Leban solution. It just that I've already invested alot of time in
the Microsoft solution and I was hoping someone had encountered this problem and
had a solution. It seems odd that Microsoft would post a solution that doesn't
work. I think I must just be missing something here.

The problem I'm having with the Leban solution is that it has to be in the front
end of the database. I would rather not have to put this file on each users
machine.

With the micorosft solution I can place a dll in the back end where I can
control things better.
 
K

Ken Snell [MVP]

I was not successful with the Microsoft method, so I've not pursued it. I am
sorry that I cannot give you some suggestions for it.

It's possible that that solution is related to the version of mouse
software? Just a wild thought, but it wouldn't be first time if yes.
--

Ken Snell
<MS ACCESS MVP>
 
M

Mark Schirle

In the solution they say you should use the Microsoft Intellmouse software. I
did load that software, but it made no difference.

thanks for your help.
 
K

Ken Snell [MVP]

There have been many modifications to Intellimouse software over past few
years.... newest versions lack some features that are in earlier versions.

Again, I'm sorry that I cannot help more here.
--

Ken Snell
<MS ACCESS MVP>
 
D

Douglas J. Steele

The dll will have to be registered on each client, regardless of where it's
located. While you could put the dll on the server, and then register it on
each user's workstation, that's not a particular sound solution, if only
because it will generate additional network traffic. I'm not sure what you
mean by stating that you could "control things better" if the dll is on the
server. You'd still likely end up have to reregister it on each client if
you changed it on the server.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)
 
M

Mark Schirle

I guess I should try asking my original question again.
I am trying to keep users from being able to scroll thru records with the mouse
wheel. The Leban solution doesn't seem to address this issue. It allows for
scrolling thru records. Does anyone have a solution that will stop a user from
being able to scroll thru records with the mouse wheel.
Thanks
 
S

Stephen Lebans

If you want to use the MS Solution then there is a modified version that
works correctly for Subforms on the MouseWheelHook Web page. Just scroll
way down to the OLDER VERSIONS area.

Why do you state that my MouseHook does not work? What particular issue
are you having with the solution?

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.
 
F

fdd

Not sure what you are taking about as Stephen Lebans' MouseHook works fine
for everyone I know.
Take it from me as someone that has struggled with the wheel problem for a
long time, Stephen's solution is the best out there.

How are you using it? and do you have the latest? version of his site.

Bruce
 
M

Mark Schirle

When I open a record for editing I use the standard
docmd.openform "frmName", stCriteria
stCriteria being "ID = " & txtID
so it opens a recordset of 1 record. The form is designed to show the fields
of just one record. Not a list of records. But when I'm on the form and
move the mouse wheel i move between the current record and a new record. I
don't want to expose a new record to the user. So I am trying to stop the
wheel from allowing this. On the solution you provide it allows for record
navigation. Now I don't expose the record navigation buttons but the wheel
still moves to a new record. I've also made allowadditions = false
with no luck. So am I missing something here. I'm using Acc97 and Windows95
however I am upgrading to Win2k very soon.
Thanks for your help!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top