Procedure Too Large - Breaking it down

[scomar411]

I've used the macro function to format a worksheet that will be used in other worksheets. Once complete I recieved the "procedure to large" message and am unsure how to "break-down" the code into smaller modules and then use to complete the task. How can I accomplish the task?

 

[Oaktree]

It's hard to advise where to break your code without seeing it, but the basic idea is this:

Sub Format_everything()
myFormat1
myFormat2
End Sub

Sub myFormat1()
'do some stuff
End Sub

Sub myFormat2()
'do other stuff
End Sub

Then, calling Format_everything() will subsequently call the other two.

 

[Padawan]

Scomar , Oaktree:

I had a similar problem like this on a major project a few years ago.

the solution I used was

Sub 1

Code here

Call Sub2
End sub



sub 2
code here
call sub3
end sub

and so on.

Then I just broke the code into relatively equal sized subs.

Is this another way to do this, or is there an inherent problem with this format?

Thanks.

 

[Oaktree]

It comes down to style.

Personally, I'd rather have one control sub like:

Sub Format_everything()
myFormat1
myFormat2
End Sub

so that it's easier to follow what the whole process is, but the snake method you're using would essentially function the same way.

 

[Padawan]

OK. I understand. Your method allows you to go to one sub as a "master" control. Sort of like a parrallel circuit.

My style is more of a series type of procedure. You could need to go through all of the procedures to debug.

THANK YOU.