a nice story..
but without the code (or the offending workbook) we can only guess.
my guess: a circular event e.g one change triggering the other..
or a cell change before recalc has completed...

(inserting a doevents may solve it, or a check that calculation is
complete...)

....the point is you need to know where :)

fire the support firm. mail me the workbook. i'll have a look


keepITcool

< email : keepitcool chello nl (with @ and .)
< homepage: http://members.chello.nl/keepitcool


Don Wiss wrote:

I have now invested many hours in this problem. A support firm my
company hires has also spent some hours. I can replicate the problem
usually, but some times it works. But with the macro silently failing,
with no error message, it gives few clues.

[snap]
I tend to think this is some shortcoming in Excel. But I haven't come
up with any workaround. I like using change events to control actions.
And I think this usage of SMALL to put them in descending order
(someone else wrote) is rather clever.

Don <donwiss at panix.com.