Organizing Macros

  • Thread starter Thread starter Takeadoe
  • Start date Start date
T

Takeadoe

Good morning,

I was hoping someone might be able to assist me in organizing my
Macros. These would be Macros that I access from the Tools menu.
They are macros that do some fancy charting. I use the same macro a
couple of times a year but for slightly different purposes. Each time
I use it, I have to customize it. I was hoping I could make a copy of
it, and rename it. Can someone tell me how I might do that?

Mike
 
Good morning,

I was hoping someone might be able to assist me in organizing my
Macros.  These would be Macros that I access from the Tools menu.
They are macros that do some fancy charting.  I use the same macro a
couple of times a year but for slightly different purposes.  Each time
I use it, I have to customize it.  I was hoping I could make a copy of
it, and rename it.  Can someone tell me how I might do that?

Mike
Click to expand...

It would be helpful to post your code and the variables desired.
 
Takeadoe wrote :
Good morning,

I was hoping someone might be able to assist me in organizing my
Macros. These would be Macros that I access from the Tools menu.
They are macros that do some fancy charting. I use the same macro a
couple of times a year but for slightly different purposes. Each time
I use it, I have to customize it. I was hoping I could make a copy of
it, and rename it. Can someone tell me how I might do that?

Mike
Click to expand...

I usually store reusable macros that I want available in PERSONAL.XLS
so Excel will load them at startup. Macros for different uses get
stored in different modules named to hint to their usage. In your case,
I'd probably name a module containing charting macros "mChartingTools"
or something like that so I'd know where to look for them later on.

To customize a single macro for varied usage I'd normally declare
arguments (variables to be passed into the macro) between the
parenthesis following the name of the macro. Optionally, I could
copy/paste a complete procedure and change its name slightly so as to
not cause a name conflict. Adding comments to describe usage is ALWAYS
standard 'best practice' behavior when coding and so I encourage you to
do same.
 
Back
Top