Johnny C
Well-known Member
- Joined
- Nov 7, 2006
- Messages
- 1,069
- Office Version
- 365
- Platform
- Windows
This isn't a problem, just curiosity.
I've got a reasonably large Excel forecast model (10Mb). I recently rebuilt the model to FAST standards, so it now uses a ton of SUMIFS over 1200 cell ranges and these feed a lot of other sheets. Calculation is Automatic.
At bottom left, where it says 'READY', it permanently says 'CALCULATE' as well. Even if I do a CalculateFullRebuild, it says CALCULATE. It didn't before I rebuilt it.
When I run a timer the time for a Calculate is the same as for a CalculateFull. This suggests Excel has just decided that there's too many formulae and links to keep track of changes when it checks the calculation tree to see what needs to be calculated by a base Calculate so has given up.
Is there some limit that has been exceeded so Excel can't keep track of what's been changed? it takes just over a second for a Calculate/Full and 5 secs for a calculatefullrebuild.
PS I know it shouldn't be in Excel but they don't have a forecasting tool and no appetite for even an Access Db, and the Risk policy is that models should conform to FAST.
I've got a reasonably large Excel forecast model (10Mb). I recently rebuilt the model to FAST standards, so it now uses a ton of SUMIFS over 1200 cell ranges and these feed a lot of other sheets. Calculation is Automatic.
At bottom left, where it says 'READY', it permanently says 'CALCULATE' as well. Even if I do a CalculateFullRebuild, it says CALCULATE. It didn't before I rebuilt it.
When I run a timer the time for a Calculate is the same as for a CalculateFull. This suggests Excel has just decided that there's too many formulae and links to keep track of changes when it checks the calculation tree to see what needs to be calculated by a base Calculate so has given up.
Is there some limit that has been exceeded so Excel can't keep track of what's been changed? it takes just over a second for a Calculate/Full and 5 secs for a calculatefullrebuild.
PS I know it shouldn't be in Excel but they don't have a forecasting tool and no appetite for even an Access Db, and the Risk policy is that models should conform to FAST.