I agree: Hmmm... I'll have to fiddle around a bit, but I doubt that I'll
find a definitive answer since it's not clear what language a given snippet
of code is written in, AND there are so many other interesting things to
explore.

Thank you for all your replies. I'll mark this Answered.

aj

"T. Valko" wrote:

Hmmm...

You bring up a good point..."at execution".

I can't say that I know *exactly* how Excel does things at the execution
level.

It would seem prudent to terminate at the first encounter of FALSE rather
than continue.

Depending on what version of Excel you have, it has formula auditing tools
which steps through the formula evaluation process. It's my understanding
that this shows the *exact* sequence of steps that Excel uses to calculate
formulas. If you evalaute a formula like:

=AND(B9<116,MOD(ROW()-9,5)=0)

You can see that Excel is evaluating every argument.


--
Biff
Microsoft Excel MVP


"aj scott" wrote in message
...
This is a total aside, but I thought all languages [at execution] would
assign FALSE to an AND statement at the first false clause encountered in
the
statement. Since it wouldn't matter if that false were followed by 200
true
clauses, why bother continuing to evaluate? But you're saying that Excel
plows right on? Does VBA? I'm quite sure VB doesn't.

aj


"T. Valko" wrote:

You're welcome. Thanks for the feedback!

=AND(B9<116,MOD(ROW()-9,5)=0)
PS I put the MOD clause before the B9 tests for efficiency's sake.

If you mean you did this:

=AND(MOD(ROW()-9,5)=0,B9<116)

It makes no difference. All the arguments are evaluated before the final
result is produced.


--
Biff
Microsoft Excel MVP