CycleTimeCha
07-22-2011, 08:24 PM
I have an application in which formulas containing user functions are inserted in cells possibly before the code for the user functions exists. This possibility is something I cannot eliminate.
The code for the user functions is eventually brought into the workbook through a process which Chip Pearson calls extensibility. One way to describe extensibility is the programmatic copying of VBA modules from one workbook to another.
If a function call-out exists before the function itself exists, #NAME? appears in the cell, as you would expect.
BUT HERE IS THE CRUX OF THE PROBLEM:
#NAME? stays in the cell, even after the code has been copied. This is true even after invoking Application.CalculateFullRebuild, which tells me Excel is failing to re-calculate cells which formerly had a #NAME? error.
Any ideas on how to get Excel to re-calculate cells which formerly had a #NAME? error?
The code for the user functions is eventually brought into the workbook through a process which Chip Pearson calls extensibility. One way to describe extensibility is the programmatic copying of VBA modules from one workbook to another.
If a function call-out exists before the function itself exists, #NAME? appears in the cell, as you would expect.
BUT HERE IS THE CRUX OF THE PROBLEM:
#NAME? stays in the cell, even after the code has been copied. This is true even after invoking Application.CalculateFullRebuild, which tells me Excel is failing to re-calculate cells which formerly had a #NAME? error.
Any ideas on how to get Excel to re-calculate cells which formerly had a #NAME? error?