I have a model which works well within Excel 2k, however in 2003 I
suffer form the problem described in this knowledgebase document
http://support.microsoft.com/?scid=kb;en-us;825011.
I have implemented the solution given in the document but the
performance decrease is unacceptable. Is there any other solution to
this problem. Before anyone asks I have calculation set to manual with
Iteration unticked and I have turned ScreenUpdating off.

Regards
Nigel

Nigel,

Instead of calculating just some cells, try calc'ing the whole sheet: that might improve
performance.

Worksheets("Sheet Name").Calculate

HTH,
Bernie
MS Excel MVP


"Nigel" wrote in message
ups.com...
I have a model which works well within Excel 2k, however in 2003 I
suffer form the problem described in this knowledgebase document
http://support.microsoft.com/?scid=kb;en-us;825011.
I have implemented the solution given in the document but the
performance decrease is unacceptable. Is there any other solution to
this problem. Before anyone asks I have calculation set to manual with
Iteration unticked and I have turned ScreenUpdating off.

Regards
Nigel

Bernie,

I really wish it was that simple. The issues that I have found so far
include:
The NormInv function has slowed down so much as to be unusable.
The LogInv function has the same issue.
The new calculation engine doesn't allow for partial range array
calculation.
I am hoping this isn't the tip of an unmanagable iceberg.

Regards
Nigel