This technique takes the functions out of Excel's precedent tracing, so that Excel doesn't call those functions when it does a worksheet recalculation. When your macro runs, it will read the value of the function from cell A145 and write that as a plain numeric value (not a formula) to cell A146.
Instead, you establish a second cell, say A146, and all your formulas reference A146. None of your Excel formulas will reference A145. For example, suppose you have an a function in cell A145. To prevent functions from resampling when your macro triggers a recalc, ensure that no functions are precedents of any cells that are affected by your Excel Solver optimization. You will see that the objective calculation is a moving target and the Excel Solver optimization will not converge on an optimum solution. To demonstrate this problem, try running Excel Solver on a model where the objective calculation is dependent on a '=RAND()' Excel function. If the functions resample, the model will not remain static during the processing of the macro, and Solver will be trying to hit a moving target.
This is exactly the requirement: The functions must not change their values during the extra worksheet recalculations.
