Run Multiple VBA Procedures from One Excel Worksheet Change Event
Question details
The user needs to run multiple VBA procedures when cells change on the same Excel worksheet.

- Product
- Microsoft Excel
- Device & OS
- not provided
- Scenario
- Separate procedures, including procedures in different modules, need to respond to changes in different worksheet ranges.
- Observed behavior
- Excel permits only one Worksheet_Change event procedure per worksheet module.
Open the workbook in a desktop version of Excel that supports VBA, and identify the worksheet and ranges each procedure should monitor. Save the workbook as an Excel Macro-Enabled Workbook (.xlsm) and enable macros if appropriate.
Call separate procedures from one Worksheet_Change event
Use one event handler to check each monitored range and call the relevant procedures, even when they are stored in standard modules.
The event procedure must be in the code module for the worksheet being monitored. The called procedures can be public procedures in standard modules and should accept a Range argument if you pass Target to them.
Disabling events while the procedures run prevents their cell edits from triggering the same event again. The cleanup block restores events if a procedure raises an error.
In Excel, open the VBA editor with Developer > Visual Basic. In Project Explorer, double-click the worksheet you want to monitor.
Replace any separate Worksheet_Change handlers in that worksheet module with one handler like this: Private Sub Worksheet_Change(ByVal Target As Range) On Error GoTo CleanUp Application.EnableEvents = False If Not Intersect(Target, Me.Range("A:A")) Is Nothing Then Macro1 Target End If If Not Intersect(Target, Me.Range("B:B")) Is Nothing Then Macro2 Target End If CleanUp: Application.EnableEvents = True If Err.Number <> 0 Then MsgBox "Macro error: " & Err.Description End Sub
Replace A:A and B:B with your monitored ranges and Macro1 and Macro2 with your procedure names. In each standard module, declare the called procedure as Public and give it a Range parameter, for example: Public Sub Macro1(ByVal Target As Range). If an existing procedure takes no arguments, call it without Target instead.
Return to the worksheet and edit cells in each monitored range. Confirm that the corresponding procedure runs; a pasted range that intersects both monitored ranges can trigger both procedures.

Work with Excel files in WPS Office
WPS Office is a free, lightweight alternative with a familiar spreadsheet interface and support for common Excel formats, making it easy to move everyday spreadsheet work. It does not fix Excel's VBA event behavior; check macro compatibility before relying on an automated workbook.

Frequently Asked Questions
Can the called VBA procedures be in different modules?
Yes. Put the single Worksheet_Change handler in the relevant worksheet's code module and call public procedures from standard modules. If you pass Target, each called procedure must accept a compatible Range argument.
What happens if a pasted range intersects both monitored columns?
Both Intersect checks can be true, so both procedures run in the order shown in the event handler. Each procedure should handle Target containing multiple cells.
Why does the code turn off Application.EnableEvents?
If a called procedure edits cells, it can trigger Worksheet_Change again. Setting Application.EnableEvents to False prevents that recursion; the cleanup block sets it back to True.
Why doesn't Worksheet_Change run when a formula recalculates?
Worksheet_Change responds to cell changes, not changes caused solely by recalculation. For recalculation-related logic, consider the Worksheet_Calculate event in the worksheet's code module.
How can I restore events if a macro stops unexpectedly?
In the VBA editor, open the Immediate window with View > Immediate Window, enter Application.EnableEvents = True, and press Enter. Then test the worksheet again.




