If anyone's interested I found the solution to the re-calculation problem -
In a word "Dirty".

There's a method called .Dirty which marks the cell as changed, which forces
a re-calculation.

Thanks to everyone for your suggestions.



"mickey" wrote:

I have a special formula in a cell, which I can cause to be calculated via
the .calculate method in Visual Basic. Unfortunately, if the cell, or any
dependencies do not change issuing another .calculate method does not cause a
re-calculation, which is a good idea in most cases (why waste CPU time
calculating a cell that hasn't changed). But as I said, without getting too
involved with the why, I have a need to FORCE a re-calculation even if the
cell has not changed. I can of course force a change, but I was hoping that
someone knew of some more elegant way around Excel's prohibition on
re-calculating cells that haven't changed.

Any useful suggestions would be greatly appreciated.