Worksheet_Change(ByVal... not working now

[John Keith]

I have the following code in a worksheet and it worked fine at the
time I first played with it. I haven't touched the workbook for a
while and now the macro is never executed. I put a breakpoint in the
code and the breakpoint is never reached. Have I done something to
disable the ability to trigger on value changes?

(I think the content and action of the code itself is not the issue
and what I have posted is actually simplified to minimize the post.
The fact remains that it appears that the macro is never invoked.)

Private Sub Worksheet_Change(ByVal Target As Range)
a = Target.Row
b = Target.Column
ColumnLetter = Left(Cells(1, b).Address(0, 0), 2 + (b <= 26))
Application.EnableEvents = False
Cells(a, 2) = Format(Now(), "mm/dd/yy")
Current_Text = Cells(a, 4)
If Len(Cur_Text) > 0 Then Cur_Text = Chr(10) & Cur_Text
New_Text = " column " & ColumnLetter & " changed"
Cells(a, 4) = Format(Now(), "m/d/yy") & New_Text & Cur_Text
Application.EnableEvents = True
End Sub

TIA



John Keith
(e-mail address removed)

 

[Don Guillett]

I just installed your macro in the sheet code and changed a cell in col a
and got
2 9/11/2009 9/11/09 column A changed

 

[John Keith]

Don,

Yes, that's exactly what it used to do for me (well, simplified as I
noted.) For some reason the code does not execute on my workbook.
Strange.

I just installed your macro in the sheet code and changed a cell in col a
and got
2 9/11/2009 9/11/09 column A changed

John Keith
(e-mail address removed)

 

[Jim Thomlinson]

Ensure that your events are not disabled...

Sub ResetEvents
Application.EnableEvents = True
end sub

Events is a persistent setting. If you switch it off the only way to
reactiveate it is to do so via code...

 

[Don Guillett]

Or leave and come back

 

[John Keith]

Ensure that your events are not disabled...

Sub ResetEvents
Application.EnableEvents = True
end sub

Events is a persistent setting. If you switch it off the only way to
reactiveate it is to do so via code...

Jim,

Thanks, I think somehow during the testing this mode must have been
been left in the wrong state.



John Keith
(e-mail address removed)