Help With Looping Macro

The Macro is so small using the call procedure probably won't do much. Possibly only solution I could think of is with a loop which changes the intersect target and runs the macro while changing the range and formula column. I highlighted in red the changing ranges.

Please Login or Register  to view this content.

Originally Posted by Richard Buttrey

Hi,

I'll take a more detailed look later - may be a couple of days.
However in essence you need to identify the common sections of your code and create a single procedure.

In the new code use variables to identify things like different ranges. You can pass variables to a procedure with a Call instruction,

Please Login or Register  to view this content.

Please Login or Register  to view this content.

The other method is to declare Public Variables and in the Control procedure assign the value to the variable before calling the MainCode. In that case you don't need to specify the values you are passing within the parentheses (), in the Control procedure or the main procedure

Hello Richard Buttrey sorry to bother, but did you have any luck trying to find a shirked version of my Macro?

Maybe it look like this

Please Login or Register  to view this content.

I just edit original code. However, in some case, you don't know how is bester because maybe someone will ask why two file has same structure (has same sheet (tab) name but different codename because user don't know what is codename) but the macro correct with one and incorrect with one.

Originally Posted by huuthang_bd

Maybe it look like this

Please Login or Register  to view this content.

Thank you so much huuthang_bd the code work perfect with just simple errors from my request. I tweaked your code a tiny bit to make it do exactly what I needed and it's running perfectly now thanks to your code. I've posted my tweaked version below in case someone else on this form might find it helpful, thank you again so much I greatly appreciate it.

Please Login or Register  to view this content.

Originally Posted by Richard Buttrey

The question is does it work? If so great.

There are often different ways of getting to the same goal.
One approach I was suggesting was to identify blocks of code that are essentially the same structure and use one block of code to which you pass variables like sheet names, ranges etc.

Incidentally it's much better practice to use VBA sheet code names rather than sheet tab names.
e.g. instead of Worksheets("Sheet3").Range... use instead Sheet3.Range
Tab names are to easily changed and code that uses them will then fail.

Thank you Richard Buttrey as well.