I'm not clear what you mean.
I mean this:

If the"[Event Procedure]"is missing, the "Form_Current()" event not occur, even if it's code is already in the class module.
BTW, I think that this issue, using the OnCurrent event of the forms, drives to infinity loop and bookmark problems.
If the goal is to display addition details in main form of the selected asset through the subform,
i recommend the usage of one more subform with the particular fields (images, descriptions etc),
controled by the subform "Asset Groups" with user-defined events between the subforms.
Underneath, you can see the code of two subforms.
The subform "Form1" fires the event when the OnCurrent event occurs and the other form(s)
going to the particular record using the value passed from this event.
Code:
Option Compare Database
Option Explicit
'Form1's class module (Ex. "Asset Groups subform". The "navigation" form)
'~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Public Event declaration
Public Event AssetChange(varID As Variant)
'
Private Sub Form_Current()
RaiseEvent AssetChange(Me.My_ID)
End Sub
Code:
Option Compare Database
Option Explicit
'Class module of any form that wants catch the Form1's event(s)
'~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Private WithEvents sForm1 As Form_Form1 'Keeps an instance of the Form1
'
Private Sub Form_Load()
Set sForm1 = Me.Parent.Form1.Form
End Sub
Private Sub Form_Unload(Cancel As Integer)
Set sForm1 = Nothing
End Sub
Private Sub sForm1_AssetChange(varID As Variant)
Me.Recordset.FindFirst "[My_ID]=" & varID
End Sub
That solves the problems of master/child links and the "Asset Group" subform can keep then link with the Main form as it was.