Not sure what you're after.
Perhaps it is something like this: you can create a function in a standard module that accepts a parameter for the Screen.ActiveControl.somePropertyHere, where the last part is the name, tag, caption or other useful property of the button that was clicked. Then in design view you can select a whole whack of buttons (what is a whack anyway?) and set the On Click event property to the name of that function. When clicked, those buttons will run said function. In that function you could use a Select Case block to determine what to do. However, you will have 105 Case statements in that block - something that I've never done to that extent. Each one of those case statements would do something different if need be. I say that because I don't know what those 105 calls to "Button" do.
There are probably other solutions; one perhaps being to use WithEvents. However, I must confess to never having used that method, and FWIK it would require you to declare 105 variables (one for each button) but don't quote me on that. Perhaps someone knows how to write a class for all command buttons that can distinguish between the 105 of concern and ignore ones that do things like open forms, but that's not me.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.