Using "Event Sinks" might be what you want.  Here's an example:

Create a class module as follows, and save it as clsTest (note that it MUST
be a class module, not an ordinary module):

'Code begins for clsTest
Option Compare Database
Option Explicit
Private WithEvents mfrm As Form
Private WithEvents mcmd1 As CommandButton
Private WithEvents mcmd2 As CommandButton
Property Set Form(ByRef Form As Form)

   Set mfrm = Form
   Set mcmd1 = mfrm!cmd1
   Set mcmd2 = mfrm!cmd2

End Property
Private Sub mcmd1_Click()

   MsgBox "Command 1 clicked in Form " & mfrm.Name

End Sub
Private Sub mcmd2_Click()

   MsgBox "Command 2 clicked in Form " & mfrm.Name

End Sub
'Code ends for clsTest

Then create a form named "Form1", give it two command buttons "cmd1" and
"cmd2" and the following code:

'Code begins for Form1
Option Compare Database
Option Explicit

Dim mobjTest1 As clsTest

Private Sub Form_Open(Cancel As Integer)

       Set mobjTest1 = New clsTest
       Set mobjTest1.Form = Me

End Sub
'Code ends for Form1

Copy Form1 and name the copy Form2.  Launch each form, click the command
buttons, and see what happens.  You should be able to see that you now have
generic code for the two forms and their command buttons which can be
applied to any form with just three lines of code.

all

bar

Baz's example is vert good --- with one exception.
It is a poor practice to use Access reserved words as names.  It can confuse
Access and create unpredictable results.

Change the name Form to something else.