UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> Mouse Wheel    
 
   
parkerkaylee
post Jul 28 2008, 11:55 AM
Post #1

UtterAccess Addict
Posts: 143



The dreaded mouse wheel...

Like many others, I want this to not cycle through records. However, it seems to take a lot (as far as libraries and keeping them in the right spot). I am developing a database for a couple of computer morons that would not follow directions if their life depended on it (for example, keeping the mousehook.dll in the right place). AND they require that the wheel NOT scroll through records. So, I'm between a rock and a hard place...

I've been looking around and found Leban's mouse wheel on and off sample. I also found Microsoft's answer to the problem (a .dll). This seems like a lot for my users to handle (they go moving stuff about, without regard to references).

I was wondering, as I didn't find anything relating to this, if you could use the Mouse Wheel event (since I'm using 2003) to reprogram the wheel to behave like something else, like the tab key, instead of trying to disable it all together?

It's only a problem for a few screens, and these users can't be trusted to do anything right (like keep a file where they found it).

This is my last effort at solving this problem. If the answer is 'use Leban', then I shall...and happily explain to these users that they are S.O.L.

Thanks for your help!
Go to the top of the page
 
+
Grafixx01
post Jul 28 2008, 12:23 PM
Post #2

UtterAccess Veteran
Posts: 450
From: Texas



I've used the mousewheel like you want to, as far as disabling it completely in a previous DB that I made. I just had to put the DLL in the C:\Windows and C:\Windows\System32 folders and then reference it in the code of the DB. It worked like a charm, nobody could do anything. I think that's your best bet. You'll just have to put the DLL files in those directories on EVERY machine that'll run the DB.
Go to the top of the page
 
+
parkerkaylee
post Jul 28 2008, 12:59 PM
Post #3

UtterAccess Addict
Posts: 143



Why both C:\WINDOWS and C:\WINDOWS\System32?
Go to the top of the page
 
+
haughsc
post Jul 28 2008, 02:22 PM
Post #4

UtterAccess Addict
Posts: 185
From: Salisbury, UK



Its not necessary to put it in the Windows directory. It can reside in the same directory as the front end of the database. This can easily be deployed to users using a simple batch file that copies the file into it (if it doesn't exist already).
Go to the top of the page
 
+
parkerkaylee
post Jul 28 2008, 02:23 PM
Post #5

UtterAccess Addict
Posts: 143



Thanks!
Go to the top of the page
 
+
Grafixx01
post Jul 28 2008, 04:10 PM
Post #6

UtterAccess Veteran
Posts: 450
From: Texas



I tried to just put the files into the C:\Windows directory and the user was still able to use the scroll. Then when I put it into the C:\Windows\System32 folder it didn't allow them to use the scroll, so I guess it'd just have to go into the system32 folder.

I just had to put it on ALL of the machines that would access the DB.
Go to the top of the page
 
+

Thank you for your support! Reply to this topicStart new topic

Jump To Forum:
 



RSS Go to Top  ·  Lo-Fi Version Time is now: 20th May 2013 - 11:34 AM