E
Edward
Hi,
I am designing a workbook that generates sheets from a macro. These
sheets are all copies of a template sheet, in which there is another
button attached to a macro. Consequently, all subsequently generated
sheets contain this button and the associated macro.
This situation works fine in theory, but practically, I'm running into
a "Not enough resources to display completely" message, which doesn't
seem to do anything other than annoy me, and calculation times are
outrageous, 2-3 seconds each time I enter a value into a cell, string
or not, precedent or not. It seems like excel is doing a full recalc
every time I change a cell.
My main problem is that system resources business, and that is the
point of my question:
Will setting up the macro as a public subprocedure in a module, while
simply calling it from the embedded sheet buttons, free up any memory
compared to the way I'm already doing it?
Thanks in advance,
Ed
xl2003
I am designing a workbook that generates sheets from a macro. These
sheets are all copies of a template sheet, in which there is another
button attached to a macro. Consequently, all subsequently generated
sheets contain this button and the associated macro.
This situation works fine in theory, but practically, I'm running into
a "Not enough resources to display completely" message, which doesn't
seem to do anything other than annoy me, and calculation times are
outrageous, 2-3 seconds each time I enter a value into a cell, string
or not, precedent or not. It seems like excel is doing a full recalc
every time I change a cell.
My main problem is that system resources business, and that is the
point of my question:
Will setting up the macro as a public subprocedure in a module, while
simply calling it from the embedded sheet buttons, free up any memory
compared to the way I'm already doing it?
Thanks in advance,
Ed
xl2003