Application.Calculation is a read-write property that is xlCalculationAutomatic or xlCalculationManual. This is what you’re calling calculationmode.

Application.CalculationState is read only, and is xlCalculationPending, xlCalculationCalculating, and xlCalculationDone. This mimics what is seen in the status bar.

You might try using DoEvents before changing Application.Calculation. to make sure Excel finishes any ongoing calculations. Sometimes I set this kind of property twice.

The only solution I could find was to use immediate mode to set the xlcalculationAutomatic followed immediately by a saving the file.

Incidentally, this work was to PREVENT Excel/VBA from changing active x control tools size, text size and/or position. I’m 99 % there, including 64 bit Excel, but have the problem with saving the mode (back to automatic). Once I solve the VBA save automatic calculate, the control tool problem will be in the past. Maybe Microsoft will have a solution too – but we need it NOW. (This problem does seem to be directly related to today’s superfast processing.)

Thanks for answering CV’s formula. The problem is in fact usually caused by a workbook stuck in manual calculation mode, which when opened changes Excel’s calculation mode to manual, and any workbook subsequently saved will save this mode for the next time it is opened, etc.

If you only have a handful of cells that exhibit this behavior, I would suspect either automatic event-driven VBA code somewhere that changes calculation mode, or some kind of worksheet corruption. Such corruption is hard to detect, and usually solved only by recreating the worksheet or workbook.

I had a recent learning mode problem with calculation and calculationmode. Be sure calculation is enabled; check that calculation mode is set to xlCalculationAutomatic. The mode is saved with the workbook, and must be reset and saved .

Take a look and see if Excel has evaluated the Count formula and replaced the formula with the result. Obviously, and according to MS experts, this cannot (should not) happen, after all this is a spread sheet. However, I have several cells (42 at the last count) specific in one workbook where this phenomenon happens repeatedly: Excel 2003 thru 2010 . The solution was to write the formula via thisworkbook workbookopen() into the troublesome cell EVERY time the spreadsheet is called as well as every time the worksheet is activated.

You’ve been lucky. In my experience, macros recorded in one class of Excel (i.e., Excel 2007 or later vs. Excel 2003 or earlier) need at least minor tweaking, and sometimes major overhaul, before they work in the other class.

What you have to do is take the macro recorded in one version, then run it in the other version, see which commands fail, then modify the code and test in both versions until the macro works everywhere.