software

I recently upgraded from Excel 2000 to 2003
I use Group amp; Outline in large spreadsheets to facilitate navigation and
reduce clutter on the screen.
In 2000 this worked well, virtually instantaneously. In 2003 it seems to
generate a recalculation each time an outline is expanded or contracted - the
status bar shows quot;Calculating cells: 100%quot;. The recalc time seems to be
related to the number of rows / columns affected, and / or the complexity of
the outline nesting, and by expansion more than contraction.
The larger the workbook and the longer the model's recalc time, the more
important the facility is to me, but the more tedious it becomes waiting for
it to happen, to the point that it's becoming more trouble than it's worth.

Does anybody know how to prevent the recalc? It doesn't respond to Escape
or any other keybard input - you just have to wait for it to do whatever it
is it's decided to do!
Brian,

I think its caused by Excel 2003 triggering a recalc whenever a row is
hidden.

You should be able to partially solve the problem by switching to Manual
calculation mode.

Charles
______________________
Decision Models
FastExcel 2.2 Beta now available
www.DecisionModels.com

quot;BrianHquot; gt; wrote in message
...
gt;I recently upgraded from Excel 2000 to 2003
gt; I use Group amp; Outline in large spreadsheets to facilitate navigation and
gt; reduce clutter on the screen.
gt; In 2000 this worked well, virtually instantaneously. In 2003 it seems to
gt; generate a recalculation each time an outline is expanded or contracted -
gt; the
gt; status bar shows quot;Calculating cells: 100%quot;. The recalc time seems to be
gt; related to the number of rows / columns affected, and / or the complexity
gt; of
gt; the outline nesting, and by expansion more than contraction.
gt; The larger the workbook and the longer the model's recalc time, the more
gt; important the facility is to me, but the more tedious it becomes waiting
gt; for
gt; it to happen, to the point that it's becoming more trouble than it's
gt; worth.
gt;
gt; Does anybody know how to prevent the recalc? It doesn't respond to Escape
gt; or any other keybard input - you just have to wait for it to do whatever
gt; it
gt; is it's decided to do!
gt;
gt;
Thanks. That works, but it's a nuisance!

Anyone know of anything else?

(And don't you just love the way each new version manages to eliminate at
least one useful feature from previouis versions and you have to find a new
work-around? At least, that's been my experince over the last 10 years or
so.)

BrianH

quot;Charles Williamsquot; wrote:

gt; Brian,
gt;
gt; I think its caused by Excel 2003 triggering a recalc whenever a row is
gt; hidden.
gt;
gt; You should be able to partially solve the problem by switching to Manual
gt; calculation mode.
gt;
gt; Charles
gt; ______________________
gt; Decision Models
gt; FastExcel 2.2 Beta now available
gt; www.DecisionModels.com
gt;
gt; quot;BrianHquot; gt; wrote in message
gt; ...
gt; gt;I recently upgraded from Excel 2000 to 2003
gt; gt; I use Group amp; Outline in large spreadsheets to facilitate navigation and
gt; gt; reduce clutter on the screen.
gt; gt; In 2000 this worked well, virtually instantaneously. In 2003 it seems to
gt; gt; generate a recalculation each time an outline is expanded or contracted -
gt; gt; the
gt; gt; status bar shows quot;Calculating cells: 100%quot;. The recalc time seems to be
gt; gt; related to the number of rows / columns affected, and / or the complexity
gt; gt; of
gt; gt; the outline nesting, and by expansion more than contraction.
gt; gt; The larger the workbook and the longer the model's recalc time, the more
gt; gt; important the facility is to me, but the more tedious it becomes waiting
gt; gt; for
gt; gt; it to happen, to the point that it's becoming more trouble than it's
gt; gt; worth.
gt; gt;
gt; gt; Does anybody know how to prevent the recalc? It doesn't respond to Escape
gt; gt; or any other keybard input - you just have to wait for it to do whatever
gt; gt; it
gt; gt; is it's decided to do!
gt; gt;
gt; gt;
gt;
gt;
gt;

Indeed it's a nuisance. Anyone any solution yet on getting the 2000 quot;wayquot; of
recalculating back. (besides downgrading...)

quot;BrianHquot; wrote:

gt; Thanks. That works, but it's a nuisance!
gt;
gt; Anyone know of anything else?
gt;
gt; (And don't you just love the way each new version manages to eliminate at
gt; least one useful feature from previouis versions and you have to find a new
gt; work-around? At least, that's been my experince over the last 10 years or
gt; so.)
gt;
gt; BrianH
gt;
gt; quot;Charles Williamsquot; wrote:
gt;
gt; gt; Brian,
gt; gt;
gt; gt; I think its caused by Excel 2003 triggering a recalc whenever a row is
gt; gt; hidden.
gt; gt;
gt; gt; You should be able to partially solve the problem by switching to Manual
gt; gt; calculation mode.
gt; gt;
gt; gt; Charles
gt; gt; ______________________
gt; gt; Decision Models
gt; gt; FastExcel 2.2 Beta now available
gt; gt; www.DecisionModels.com
gt; gt;
gt; gt; quot;BrianHquot; gt; wrote in message
gt; gt; ...
gt; gt; gt;I recently upgraded from Excel 2000 to 2003
gt; gt; gt; I use Group amp; Outline in large spreadsheets to facilitate navigation and
gt; gt; gt; reduce clutter on the screen.
gt; gt; gt; In 2000 this worked well, virtually instantaneously. In 2003 it seems to
gt; gt; gt; generate a recalculation each time an outline is expanded or contracted -
gt; gt; gt; the
gt; gt; gt; status bar shows quot;Calculating cells: 100%quot;. The recalc time seems to be
gt; gt; gt; related to the number of rows / columns affected, and / or the complexity
gt; gt; gt; of
gt; gt; gt; the outline nesting, and by expansion more than contraction.
gt; gt; gt; The larger the workbook and the longer the model's recalc time, the more
gt; gt; gt; important the facility is to me, but the more tedious it becomes waiting
gt; gt; gt; for
gt; gt; gt; it to happen, to the point that it's becoming more trouble than it's
gt; gt; gt; worth.
gt; gt; gt;
gt; gt; gt; Does anybody know how to prevent the recalc? It doesn't respond to Escape
gt; gt; gt; or any other keybard input - you just have to wait for it to do whatever
gt; gt; gt; it
gt; gt; gt; is it's decided to do!
gt; gt; gt;
gt; gt; gt;
gt; gt;
gt; gt;
gt; gt;