I don't believe you can have 2 or more Worksheet_SelectionChange event handlers in the same worksheet class module. It's also unclear why you'd want the 2nd rather than putting its only statement into the first so-named event handler and moving lRow inside that procedure.
Next, tangent: if it made sense for lRow to be external to any procedure, it may be better to declare it as Private rather than Public. Private for declarations outside procedures means available to all procedures within that module, but not accessible in other modules. I can't imagine you'd want to access lRow from code in other modules.
Why not
?
Note: if the last nonblank cell in col A were A1234, then if you select A1235, this event handler will put formulas into T1235, Y1235, Z1235, etc. If you don't enter anything in cell A1235, then select, say, C1220, then select A1235 again, the event handler will happily reenter the same formula again in all the indicated columns in row 1235. Do you want to enter those formulas only when all cells in the indicated columns in row 1235 are blank?
ADDED: continuation from above, A1234 the bottommost nonblank cell in col A, if you select A1236, nothing happens. Would you want formulas copied into rows 1235 and 1236 instead?
Bookmarks