Scroll wheels

onlyty

Registered User.
Local time
Today, 23:06
Joined
Jul 22, 2008
Messages
45
Hi

just a quickie (I Hope) I have a form showing different courses with a subform for adding students to the courses.my problem is that people are using the scroll wheel on the mouse to add students to the list and this is scrolling to different courses instead - people are therefore being booked onto the wrong courses without the user noticing what they have done.

can a disable the scroll wheel from working on the main form.

thanks
 
I think your best bet is to limit the record the user can access in the forms underying recordsource. Trying to disable the scroll wheel is a pain... :)
 
OnMouseWheel event maybe? There's various pieces of code out there on the net, that will do this too. I've even seen one that requires a DLL to be loaded!
 
thank you Kenhigg but could you please give me some more information on how?

sorry access not my strong point!
 
ken's not here so i'll chime in.

instead of giving the user a form that has all the courses in it (plus subform data) just give them one course at a time.

so, you'll need two forms.

the first form will contain a simple *list* of *courses only* that shows only the data they need to make a decision as to which course they want to edit/add students to. the user selects *one* course, clicks a button and you send them to the second form that only contains that one course (+ optional details) + subform.

scrolling will still work but they'll go to an empty record and should easily get themselves back.

there are many ways to approach this but this is the simplest. you can, for example, easily stop someone from scrolling to another record if the user has already started to edit the current record, but if they haven't started editing then you're stuck. giving them one record at a time is safe and good practice.
 
thanks wazz sounds like a good idea - I can see the logic will work on it tomorrow and let you know.
 
not sure where i get it from - somewhere here

i am using a dll called mousehook, with 1 module to include in your database, this turns the mousewheel on/off perfectly
 
Don't you have to account for the dll in your distributed front-ends?
 
Don't you have to account for the dll in your distributed front-ends?
Not if you deploy it to the EndUser with a fancy BAT file that will copy the DLL to system32 and register with Windows.
 
Howzit

Lebans solution uses a dll called mousehook. One of Leban suggestions is to put the dll in the current db location. I put it in a shared location (usually where the back end sits) so I don't have these dlls all over the place. I changed his code to look at the shared locations as opposed to the current location...

Irt works perfectly...
 

Users who are viewing this thread

Back
Top Bottom