Ok, I have disabled the right click button in my application and that part is easy enough but how do I disable the center roller ball on the mouse? I do not want the user to be able to just scroll through the records using the roller ball. Can someone help me with this? Is there a check box I'm missing that will disable this feature as well? Thanks.
This is not what I mean. I want them to be able to still use their mouse and that kind of thing. I'm talking about the center roller that allows you to scroll down the screen and through records and things like that. A lot of people use them when viewing web pages or large files rather than using the scroll bar to the far right of the screen. I'm not talking about the ball at the bottom of the mouse.
That is a little drastic but I may consider it The reason I need to do this is because I do not want the user to be in the user form and entering the appropriate information that they will be putting into the table and accidentally bump the scroller ball and all of a sudden they are on a different record all together without even realizing it. Through testing, it's already happened a couple of times and it's frustrating to me as the developer because they think something drastic has happen when all they've done is moved to a different record without realizing it. So I figured that if I could disable the scroller ball then we'd be good to go. I've already disabled the right click feature so I'm pretty sure that the ball can be disabled(without harm to the user) but I'm just missing it somewhere. Any ideas? I've thought about just putting in cheap mouses that don't have scroll balls at all on the machines that the users will be using but would rather do it the right way first
That solution requires the insatllation of a DLL, can't see every systems team accepting that requirement. Certainly I know I'd have no chance of installing a DLL. I think blindmans suggestion is the best
find out what event is being triggered by the wheel move and inhibit it.
Both are good suggestions and will work. I have the ability to install DLL's, though, so this seems like the best solution for my application but both of the ideas will probably work. As long as the user cannot user their scroller ball, I'm fine With the group I'm writing this for, I've found that the fewer ways you give them to do things the better off we all are So I've resorted to making sure that there is only one way to do everything so that there is less likelihood of something getting messed up or the user getting confused
The systems support team at my place of work do not let any / everyone install DLL's or anthing that may effect the suppositry [aka repository] on the grounds that it may affect the systems and corrupt the standard platform. There is no write access to windows/system & system32, no ability to install any software, unless it affects only that directory/application
regular auditing check for rogue DLL's and removes them without warning. In short can't / won't
Am I missing something? Why don't you set the Default View property of your form to "Single Form," and turn off the scroll bars and record navigation buttons. Then program new homemade navigation buttons to perform only deliberate record jumpings. That way no one will accidentally jump to another record.