wheel mouse changes from XP and 2003 to 2007

[ArielZusya]

I've got a form used for data entry in a database. Users with XP, 2003, and
2007 all use the database and the form in question. The users in XP and 2003
are able to use the wheel mouse to scroll between records. For some reason,
in 2007 this is no longer an option. Is there a setting somewhere in 2007 of
which I'm not yet aware? Do I need to write code to enable the
wheel-mouse-scrolling? Is there a way to do this so it won't impact XP and
2003 (ie won't get rid of the scrolling functionality that is defaulted in
2003 and XP)? Thanks!

 

[Douglas J. Steele]

In Access 2007, you have to use the form's MouseWheel event (see what Allen
Browne has at http://www.allenbrowne.com/ser-70.html for details).

I believe you'll need to have a separate version of the application for
Access 2007 users.

 

[ArielZusya]

Excellent! Thanks! That's exactly what I was looking for. It appears from
Allen Browne's code that he has a section in there that looks for Access 12
and if the user isn't using 12 it does nothing... in other words, 2003 and
previous will ignore the new code. Glad I won't have to maintain two DBs on
this project... one is plenty. *GRIN* Thanks again!

 

[Douglas J. Steele]

Unfortunately, when you've got users with different versions of Access, you
often have no choice but to have a different version of the application for
each version of Access due to problems with the References collection.

Remember that your application should be split into a front-end (containing
the queries, forms, reports, macros and modules), linked to a back-end
(containing the tables and relations). Only the back-end should be on the
server: each user should have his/her own copy of the front-end, ideally on
his/her hard drive. You'd do the development in the older version of Access,
then convert up to each newer version before releasing.

 

[Allen Browne]

It's been almost a year since I wrote this, Doug, but from memory, I think
Access 2007 creates the property on the form (in your MDB), and triggers the
event.

What happens in previous versions, is that the property now exists, but is
ignored, i.e. the earlier versions don't trigger the event. Consequently,
the old behavior occurs in the old versions, and the code simulates that
behavior in the new version.

 

[Douglas J. Steele]

I'm not doubting that your code will work in both versions, Allen.

My point is that trying to use the same front-end with multiple versions of
Access may not always work.