It's been a few months, but wanted to confirm Babycat's issue, as I am having the same exact thing. Apparently it is a rare issue because I haven't been able to find any other help tickets on other sites. I joined here specifically so I could respond to this thread.
That little chirping sound is supposed indicate that I have done something that Access finds unpleasant (ie typing in a read-only field, or similar). Similar to Babycat, I did my own analysis, and can confirm a few things:
1) It's not dependent on the mouse itself - I tried two different mice (one cabled and one wireless) with the same results. I tried experimenting with the middle clicking of the mouse wheel and that doesn't appear to change the issue. I tried updating the mouse drivers, and that didn't help.
2) When scrolling using the mouse wheel over a table, if I click in a field and then scroll, I get the sound. I've seen this on both tables and joins. It happens too on multiple data types (numbers, long and short strings). Happens on both null fields and populated. I have not been able to get it to happen on check-box Boolean fields.
3) It isn't an all-the-time thing. I can click on the same field and scroll up and down, and sometimes it will happen immediately, and other times it won't for several scrolls, and then other times it won't at all.
4) Given that currently I can't get it to throw on Boolean fields, I wonder if it is indicating that I am trying to "type" some kind of invisible characters when I scroll, and that it doesn't like them. And that it doesn't happen in a Boolean field because such a field doesn't accept text or numbers.
5) It is new behavior. I work in Access every day of the week, usually for hours at a time. It's one of my primary job duties, as the admin of multiple Access databases. I believe that this behavior has only started in the last week. That said, I typically listen to music on NC headphones most of the day, so it is possible that this behavior has existed for longer than I realize.
6) I've been able to replicate the issue now on three independent Access databases. I have seen it on both local and remote databases. I have not been able to replicate the issue outside of Access.
Babycat, did you ever figure out what might be causing the issue? This is such an odd issue. It fortunately doesn't appear to be corrupting anything (I hope), but I would like to get it resolved.
I can think of a couple other things I'd like to try. I'd like to check on a user work station and see if I can replicate the issue one a totally different machine interface. I will be onsite tomorrow, and will attempt then. Thank you.