This could happen for any number of reasons. For instance, if you use
SendObject to generate an e-mail, then close the e-mail without sending it,
you will get the error message. If you use error trapping you can figure
out which event is generating the message. For instance:
Private Sub Form_Current()
On Error GoTo ProcErr
'Your code
ProcExit:
Exit Sub
ProcErr:
msgbox "Error #" & Err.Number & ", " & Err.Description & ":
Form_Current"
Resume ProcExit
End Sub
If the event is in YourTextBox_AfterUpdate, substitute that for Form_Current
in the msgbox line of code. Now when you get an error message you will know
its exact source.
Yes, there is something specific you are doing or not doing, but without
more information it is not possible to know just what that may be. If you
can identify and describe a specific instance of the error's occurence it
will be much easier to know what needs to be done to fix it.
