Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Hello,
I've got a bit of an Excel programming problem. I really need to avoid having the worksheet recalculate until the macro I'm running is done. To do so, I've been using the command: Application.Calculation = xlCalculationManual It has been working fine, too, until I added more calculated data (using a UDF) to the worksheet. Now the function just does not work. Adding a watch to Application.Calculation shows that the value does not change after it is explicitly set to xlCalculationManual. And adding "Debug.Assert Application.Calculation = xlCalculationManual" after setting the Calculation mode always causes that line to trigger the debugger. Does anyone have any idea what can be causing this? Does Excel have any conditions that must be satisfied before the calculation mode can be toggled? Thanks, David |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
VBA Application.xlCalculationManual | Excel Programming | |||
Application.Calculation = xlCalculationManual fails | Excel Programming | |||
Application.Calculation = xlCalculationManual mystery | Excel Programming | |||
How to set in XLA calculation on xlCalculationManual | Excel Programming | |||
Application.Calculation=xlCalculationManual causing run time error? | Excel Programming |