mouse scroll wheel quesiton

DBinPhilly

Registered User.
Local time
Yesterday, 17:58
Joined
May 21, 2013
Messages
42
I remember in earlier versions of MS Access (95 & 2000), a user could corrupt a table with a memo field by using the scroll wheel of the mouse and essentially scrolling right out of the record.

This is in a bound form with the cycle property set as Current Record.

The problem appeared to be resolved with MS Access 2003, but a number of users who have moved to 2007 & 2010 are now complaining of corruption problems.

Are other developers familiar with this problem and is there a fix, like disabling the scroll wheel?

I'm not sure I've identified what is causing the corruption problem. This is a theory I'm working on.
 
First and foremost, the first thing to look at with corruption is

1. Do you have the database split to a backend (tables only) and a frontend (everything else)?
2. If not, it needs to be done. If so, does EACH USER have a copy of the frontend on their machine. If not, it needs to be. You should not have multiple users using the same database file from a central location.

Read this for more about why that is important.
http://www.kallal.ca/Articles/split/index.htm
 
First and foremost, the first thing to look at with corruption is

1. Do you have the database split to a backend (tables only) and a frontend (everything else)?
2. If not, it needs to be done. If so, does EACH USER have a copy of the frontend on their machine. If not, it needs to be. You should not have multiple users using the same database file from a central location.

Read this for more about why that is important.
http://www.kallal.ca/Articles/split/index.htm

sorry - did that from the Access 95 era. Each user has his/her own front end on their individual work stations. Back end on the Server or NAS device.
 
In 2007 and 2010, there is an event for the scroll wheel which can be either used or ignored. If you are using an add-in to enable scroll wheel stuff, I would suggest removing that and then modifying your form's scroll wheel event to do what you want it to do.
 
In 2007 and 2010, there is an event for the scroll wheel which can be either used or ignored. If you are using an add-in to enable scroll wheel stuff, I would suggest removing that and then modifying your form's scroll wheel event to do what you want it to do.
sorry - supremely ignorant of any scroll wheel event. So used to worrying about the scroll wheel from prior experience, I wouldn't use it anyway.
I would prefer to disable the computer reading the scroll wheel when in MS Access, if such a thing is possible.
 
I have tried everything I can (Access 2007) to get the mouse wheel to do anything while in a form. It won't unless you add code to the On Mouse Wheel event. So, any corruption isn't likely coming from that but is something else.
 
yes, I fear that you are right.

Sure wish I could determine what is going wrong.
 
Are the frontends corrupting or the backend? If the frontend it usually is due to a connection that drops, even for milliseconds. But if it is the backend, how big is it and has Compact and Repair been run on it lately? If not, it should be. Also, if you are getting close to the 2Gb mark it could cause strange stuff to happen.
 
It's the back end corrupting, usually a single record. The database is not large, under 100Mb.
 

Users who are viewing this thread

Back
Top Bottom