I have a 14mb excel template with approximately 100 worksheets. The
template was developed in Windows XP using Excel 2002. All excel files
created from the template are stored as Excel 2002. Files developed
from the template in Excel 2002 work fine. When a copy of the template
is made and the copy of the template is populated, the size of the
file expands to 20mb.

I recently upgraded from Windows XP with Excel 2002 to Windows XP with
Excel 2003. Apparently, in Excel 2003, the hiding of rows and columns
behaves like an activating event where automatic calculations are
concerned. When a row or column is hidden, the entire application
calculates, if the default is set to automatic calculation. If 100
rows are hidden, one row at a time, the application will calculate 100
times.

So, I changed the code in each relevant worksheet to turn the
automatic calculation off whenever row(s) and/or column(s) are hidden.
The automatic calculation is turned back on after the code that hides
the row(s) and/or column(s) is finished.

This code change is the only difference that exists between the
template that exists in Excel 2002 and Excel 2003.

When an old file that was developed under Excel 2002 is called up in
Excel 2003, the CPU will sometimes spike to 100% and the entire
application will freeze indefinitely. After sampling some files, I
concluded that this occurs about 20% of the time.

When I reboot and then open the very same file that previously froze,
the file will most often open without freezing. And, sometimes, an
Excel 2002 file that previously opened without incident in Excel 2003
will freeze.

Might anyone have encountered this problem upon moving from Excel 2002
to Excel 2003 (or a later version of Excel)? Can you please provide me
with some insight that might help me to alleviate this problem.

Thank you for your time and consideration!

Michael

I believe when a file that was saved in an earlier version of excel is opened
in a later version, it is recalculated entirely upon opening. that
explanation may not totally explain you situation, but it sounds like it is a
consideration.

In xl 2003, the subtotal function was enriched to allow consideration (or
exclusion actually) of hidden rows, even when they are not hidden by a
filter. This would require a calculate event to be initiated when a row is
hidden.

--
Regards,
Tom Ogilvy


" wrote:

I have a 14mb excel template with approximately 100 worksheets. The
template was developed in Windows XP using Excel 2002. All excel files
created from the template are stored as Excel 2002. Files developed
from the template in Excel 2002 work fine. When a copy of the template
is made and the copy of the template is populated, the size of the
file expands to 20mb.

I recently upgraded from Windows XP with Excel 2002 to Windows XP with
Excel 2003. Apparently, in Excel 2003, the hiding of rows and columns
behaves like an activating event where automatic calculations are
concerned. When a row or column is hidden, the entire application
calculates, if the default is set to automatic calculation. If 100
rows are hidden, one row at a time, the application will calculate 100
times.

So, I changed the code in each relevant worksheet to turn the
automatic calculation off whenever row(s) and/or column(s) are hidden.
The automatic calculation is turned back on after the code that hides
the row(s) and/or column(s) is finished.

This code change is the only difference that exists between the
template that exists in Excel 2002 and Excel 2003.

When an old file that was developed under Excel 2002 is called up in
Excel 2003, the CPU will sometimes spike to 100% and the entire
application will freeze indefinitely. After sampling some files, I
concluded that this occurs about 20% of the time.

When I reboot and then open the very same file that previously froze,
the file will most often open without freezing. And, sometimes, an
Excel 2002 file that previously opened without incident in Excel 2003
will freeze.

Might anyone have encountered this problem upon moving from Excel 2002
to Excel 2003 (or a later version of Excel)? Can you please provide me
with some insight that might help me to alleviate this problem.

Thank you for your time and consideration!

Michael