Resume Next returning to original line of error (#2486)

Giganews Newsgroups
Subject: Resume Next returning to original line of error (#2486)
Posted by:  Danny J. Lesandrini (dlesandri…
Date: Thu, 3 Aug 2006

How is it possible that VBA could ERR out on the same line 3 times in 5 seconds?
Below are the logs for two errors that happened one right after the other and you can
see that the same line is logged thrice for each function, each in a 5 second range.

Error is always #2486:  You can't carry out this action at the present time.

ErrDateTime          Line    Function
7/31/2006 9:01:32  275    cmdOpen
7/31/2006 9:01:31  275    cmdOpen
7/31/2006 9:01:28  275    cmdOpen

7/31/2006 9:01:22  3145  SSN_DblClick
7/31/2006 9:01:19  3145  SSN_DblClick
7/31/2006 9:01:17  3145  SSN_DblClick

Here's the code for the error on line 3145.  All it's trying to do is open a form with the
DoCmd.OpenForm method.  I omitted some of the code, but I don't think the code is
causing the error.

Regardless of what the code does, Why does the Resume Next in the error trap return
the processing to line 3145?  Has anyone ever seen anything like this before?

3096    On Error GoTo Err_Handler
3103    If Not IsNull(Me![SSN]) Then
3110        If Me.Dirty = True Then Me.Dirty = False
3138        strCriteria = "[SSN] = '" & Me![SSN] & "'"
3145        DoCmd.OpenForm "frmEmployees", , , strCriteria
3152    End If
3159    Exit Sub
3166    UpdateWebErrorLog Err.Number, Err.Description, Erl
3173    Resume Next

This pattern repeats itself for seven different completely functions with nothing obvious
in common.  The user has reported that when she gets this error (#2486) the system
completely freezes and she must terminate MSAccess.exe to get back to work.

I've searched Google for posts about Error #2486 and have implemented everything I found.
She sees the errors less frequently now that I found and removed references to the boolean
value of checkboxes:  If Me!chkValid = True Then  instead of  If Me!chkValid = Then

The crash/freeze doesn't happen so often anymore (once a day instead of once an hour)
but these errors are still being logged.  Any ideas?


Danny J. Lesandrini