Can/should you put Worksheet code into a standard module?

I have a workbook with 11 worksheets with the exact same format with Worsheet_Change and Worksheet_SelectionChange vba behind it. After I originally created the first worksheet, I simply copied it to the remaining ten worksheets. I’m making some changes to that code now and I wondered if it was possible to move the code to a standard module and call it from the individual worksheets? That way I only have to change the code in one place. The worksheet code needs to identify the: 1) row, 2) column, 3) value, and 4) range name of the selected/changed range. Questions:

- Is this a bad idea / what are the trade-offs for this plan?
- As long as I fully qualify the Target, I believe the code should work in a standard module. Does anyone see anything else I would need for this plan?

Finally, I noticed my change event is: Private Sub Worksheet_Change(ByVal Target As Excel.Range) – probably because I found some of the code on the internet. Using the dropdown to create it new the code is: Private Sub Worksheet_Change(ByVal Private Sub Worksheet_Change(ByVal Target As Range)). What is the significant of “Target As Range” vs. “Target As Excel.Range?”

Thanks for reading and any help

Thanks for the feedback!

Interesting idea jaslake – I wouldn’t have thought of that. Actually the 11 I mentioned are the same, three others are the identical to each other and the remaining half dozen are unique. A select case on sh.name will work to exclude worksheets as necessary. Is that the best way to do that? Thanks.

I'm with you - Thanks!