You might want to simply eyeball the Form's Code Module; I've seen the error message
Return without GoSub
before when the developer had copied a procedure from one Form and pasted it into another Form, accidentally doing so in the middle of an existing procedure, something like this:
Code:
Private Sub AddClient_Click()
On Error GoTo Err_AddClient_Click
DoCmd.GoToRecord , , acNewRec
Private Sub CancelNewRecord_Click()
On Error GoTo Err_CancelNewRecord_Click
Me.Undo
Exit_CancelNewRecord_Click:
Exit Sub
Err_CancelNewRecord_Click:
MsgBox Err.Description
Resume Exit_CancelNewRecord_Click
End Sub
Exit_AddClient_Click:
Exit Sub
Err_AddClient_Click:
MsgBox Err.Description
Resume Exit_AddClient_Click
End Sub
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007