ms access 2010 and wheel mouse scroll support..[solved]

[vhelp]

solved -- see post # 5

i have searched google for the info but can't find any solutions.

at work, i have office pro on two machines, A 2003 and B 2010.

in forms view (I design many forms) for 2003 the wheel mouse scrolling works. but in 2010 on other computer, it does not.

does anyone know the secret to activating the wheel mouse scrolling in forms view for office pro 2010 ?

thank you in advanced.

[TreeTops]

In Word or Excel? I ask because you can design forms in both of those programs.

[Bjs]

3 seconds in google brings this from ms

Use the work around as it was removed to reduce user confusion.

[TreeTops]

And I retract my reply. I now see he was using Access not Word or Excel.

[vhelp]

resolved -

thanks for your suggestion (below), Bjs.

the solution here http://support.microsoft.com/en-us/kb/2458709 worked perfectly. see below.

i don't get it, i mean, i search many weeks, mostly evenings when i was bored, here and there a little, and did not find the solution. but you found the answer in like 5 seconds. anyway. m$ decision to pull it is not a good one. not when the actual root of the problem had to do with the poor design of the wheel-mouse, having no real click-stop (for lack of better term) so it was easy to tap it by mistake and causing the form page to update the record unintentionally. i had that problem too, back in the early days of access 2003, but solved it by getting a real mouse. i have to this day, the Logitech 810 (or 410) mouse, which supports two intensity settings for the wheel. one for a more tougher click-stop feel, and another for a smooth scrolling wheel.

Workaround: 

You can continue to use your mouse wheel in Form View in Access 2007 and in Access 2010. To do this, enable
your database, or move it to a trusted location. Then, follow these steps:

1. Open the form in Design View.
2. Use the Alt+F11 key combination, or click View Code in the Tools group on the Ribbon, to open the Microsoft
   Visual Basic editor window. 
3. Paste the following code into the code window.

Private Sub Form_MouseWheel(ByVal Page As Boolean, ByVal Count As Long)
  If Not Me.Dirty Then
    If (Count < 0) And (Me.CurrentRecord > 1) Then
      DoCmd.GoToRecord , , acPrevious       
      ElseIf (Count > 0) And (Me.CurrentRecord <= Me.Recordset.RecordCount) Then           
        DoCmd.GoToRecord , , acNext
      End If
  Else
    MsgBox "The record has changed. Save the current record before moving to another record."
  End If
End Sub

This code forces the user to save a record in which changes were made before the user scrolls to another
record. One of the main reasons for the change in the scroll behavior was that users would use the mouse
wheel to scroll through records and automatically and unexpectedly save their changes to their record.

[Bjs]

Yes ms made decisions that suited at best a minority group while the majority were happy.

On the bright side it made more work for me.

[JErickson]

Question for you all on this , we are running a DB off of a server that is used by up to 8 different people at the same time , and we have a mix of windows 7 and windows xp which means access 2003 and access 2010 , now with all of that said , I have implemented the fix listed below to get the scroll wheel to work on the 2010 machine but the problem I have now is on the older versions it skips every other record so you will only see the even or the odd records depending on where you start your search .. and ideas on how to fix that , I have been searching high and low with no luck , any help would be great , thanks by the way we are in the process of moving everything to windows 7 but it takes time and testing to be sure all the bugs are out as we are working in an emergency dispatch center

[TreeTops]

I suspect that once you get everyone up to speed using Win 7 & Access 2010 then your problems will go away. There are differences in the coding between versions so that could be causing that skipping of records.

[Bjs]

Distribution might be the key to replace 2003 > Microsoft Access 2010 Runtime

This link explains in reasonable detail how things work

Set it up this way for all users should remove the xp issue and it will make the migration of older systems being replaced a pinch.