Have you tried setting Application.Calculation to manual, making the changes and then setting it back to automatic?

This would not require a flag in the second workbook.

--
Tim Williams
Palo Alto, CA


"Mark VII" wrote in message ...
I have a utility program contained in one Excel workbook that opens and
modifies another workbook. I'd like the utility program to be able to set
the value of a variable in the second workbook.

To put this in context, when the utility program makes certain changes, it
fires the Worksheet Change event in the in the second workbook. This is
creating havoc with performance. I want to be able to add a logic branch to
the Worksheet Change sub to bypass its logic under these circumstances.

I've created a public property in the second workbook, but where I'm
stumbling is how to build the right object references so the utility program
can set the property. Any suggestions?

TIA...
Mark