MouseWheel Event stopped working properly

[Welshgasman]

This just came up in my feed.
https://youtu.be/WdAdbHJiFCU?si=jlROrVloysHCA0dM

[isladogs]

Yes I've seen Daniel's video. I hadn't mentioned it as the OP already knows everything in there.

There is also a 4th report as MS Answers forum: https://answers.microsoft.com/en-us/...8-3d09f91b827c
This references some old code by the venerable Allen Browne which was designed to allow mouse wheel scroll in single forms but which no longer works in A365.

[isladogs]

The Access team have been able to replicate the Count bug with the repro database I sent them and have confirmed that it will be fixed.

This old article may be of interest: Can't scroll records with mouse wheel - Microsoft 365 Apps | Microsoft Learn as it explains why the mousewheel behaviour was deliberately changed in A2007/A2010.

Although not the point of this thread, I still cannot see how the Page argument would ever be true.

[isladogs]

News from the Access team:
The mouse wheel issue will be fixed in version 2501, which will be available next week (W/C 27 Jan)
My related article on the Access Forever blog site will be updated again when the release date and build number are known


The Beta Channel should be fixed at around the same time

[Miles R]

I have just downloaded the latest Access Version 2501 and can confirm that the bug has been fixed.
Also, the Count in the Mouse Wheel event is showing positive or negative values depending on which way the mouse is rotated.
Text boxes with Normal Text can be scrolled using the mouse wheel, but Rich Text boxes still can't, but I have got round that by issuing Send Keys commands depending on the Count value. This also works again.

[isladogs]

I'm somewhat confused by your reply. Which channel / build are you on?

Current Channel is still on version 2412 Build 18324.20000 and has not been fixed yet. Version 2501 with the fix will be released next week
Current Channel (Preview) is on version 2501 build 18429.20114. Has that been fixed?
Beta Channel is on Version 2502 (Build 18516.20000). Fix due next week (hopefully)

[Miles R]

Colin,

The version I am on is Version 2501 (Build 18429.20114) and it says Current Channel - nothing about Preview.
Maybe I got it early.
Anyway, it is working.

[isladogs]

According to the MS website, that is Current Channel (Preview)
Update History for Office Current Channel (Preview) - Office release notes | Microsoft Learn

The latest Current Channel release was on 16 Jan - version 2412 build 18324.20194
Release notes for Current Channel releases - Office release notes | Microsoft Learn

[Miles R]

Colin,

There is no indication that I am on Current Channel Preview, not that it matters to me particularly. The main thing is I have already got the bug fix.

[isladogs]

Strange but from the info on the website, you must be on Current Channel (Preview).
It wouldn't be the first time that Office misreported the channel

If you want the definitive answer, download and run my free Access/Windows Version Check Add-In app



FWIW, I'm on the Beta Channel and haven't got the fix yet!

[isladogs]

The fix is now available in the Current Channel version 2501 (build 18429.20132) released on Thursday 30 January.
It was also fixed in Current Channel (Preview) version 2501 (Build 18429.20114) released on Friday 24 January.
However, the fix is not yet available in the Beta Channel.

I have just updated my article on the AccessForever blog site