Thanks again for taking the time to reply. I've come up with a couple
more ideas to try ... one of which is an alternative approach to
conditional formatting -- that additional calculation load I suspect is
quite significant in this case.

I'm half afraid to try a code cleaner .... I started this project
knowing nearly nothing about Excel or VBA ... much of that early code is
still in use <grin.

Thanks again!

Didn't have my spectacles on at the time!


What!? That happens to you, too?!

--
Clif

"AltaEgo" <Somewhere@NotHere wrote in message
...
See in line
--
Steve

"Clif McIrvin" wrote in message
...

Looking down below your reply I see that line wrap broke apart my
debug.print lines;

Didn't have my spectacles on at the time!


The trouble seems to be that *other* functions (which have been
working flawlessly for months) suddenly fail without generating any
error message when I set up the conditional formatting. Again, from
my OP:



When my new function / conditional formatting is active,

Excel has additional calculation load.

**only the first three debug.print statements are executed**.

I discovered this by single stepping through some of my other, now
failing, code. While stepping through the code below, F8 would stop
at 10 and 20, but when pressing F8 on line 20 the debugger would go
inactive and return to the "no code executing" state.

Sorry, cannot help.


Any other ideas for me to try?


I doubt this will help but you might try VBA code cleaner:

http://www.appspro.com/Utilities/CodeCleaner.htm


--
Steve



--
Clif