I have several macros that need to be run in progression. Combining them
would make for too long macros. The problem is that when the second macro is
called, all memory is lost (wbk1 = "xxxxxxx.xls") etc. Is there a global
declaration that can be made for each macro in the progression to keep the
assignments?

Thanks,

Jim

declare the macro in a general module at the top outside of any procedure

Public wbk1 as String

for example.

--
Regards,
Tom Ogilvy


"Jim Jackson" wrote:

I have several macros that need to be run in progression. Combining them
would make for too long macros. The problem is that when the second macro is
called, all memory is lost (wbk1 = "xxxxxxx.xls") etc. Is there a global
declaration that can be made for each macro in the progression to keep the
assignments?

Thanks,

Jim

I knew it had to be simple. Thanks, Tom.

--
Best wishes,

Jim


"Tom Ogilvy" wrote:

declare the macro in a general module at the top outside of any procedure

Public wbk1 as String

for example.

--
Regards,
Tom Ogilvy


"Jim Jackson" wrote:

I have several macros that need to be run in progression. Combining them
would make for too long macros. The problem is that when the second macro is
called, all memory is lost (wbk1 = "xxxxxxx.xls") etc. Is there a global
declaration that can be made for each macro in the progression to keep the
assignments?

Thanks,

Jim