I set up a test based on your description of how your code is organized. I
find that if the Exit Sub executes in the called procedure, which indicates
the input data could not process, then the macro completes and leaves the
target cell, which initiated the process, in edit mode. This is normal. If
double click in the same cell, it does nothing because it is in edit mode
for that cell. But, if I click in a different cell in the same column, or
the alternate column (1 or 4), then it will initiate the macro. This is all
normal behavior. You could probably add a line in your called code like:

Target.offset(0, 1).Select

Put it just before the Exit Sub line and it will take the original cell out
of edit mode.

"goodfish" wrote in message
...
Hello people!
I have a problem with a double click event:
Basically the following code works to start one of two macros (according
to
which cell I double click)

Private Sub Worksheet_BeforeDoubleClick(ByVal _
Target As Range, Cancel As Boolean)
Dim dcCell As Range

If Target.Value 0 Then
Cancel = True
Else: Exit Sub
End If
If Target.Column = 1 Then
Call POtoContract(dcCell:=Target)
Else
If Target.Column = 4 Then
Call copytableline(cyCell:=Target)

End If
End If
End Sub

Now at one point in the "called" macro the user is asked to input a name,
if
he spells the name wrong a message box warns the user and then the sub
exits.
After that if I try to double click again it goes into editing and ignores
the double click event macro until I restart the workbook.
Does anyone know what is wrong?
Thanks for any help,
Joe.