Quote Originally Posted by LaVolpe View Post
Just FYI. This topic is also discussed in the VB FAQ section

And regarding the "expression too complex" bug mentioned by Olaf in post #6, that is also addressed
Seems that in the FAQ-section the "Not Not check" is still regarded as a "good way to approach this",
with a dubious workaround for the IDE - and the statement, that the "Error will not happen in a compiled App".

Well, maybe not in the small TestApp the poster has checked, but I remember quite clearly that in a UseNet-
discussion about a decade ago, we identified the Not Not check as the cause of "Expression too complex"-
errors, a Developer reported "as happening in a compiled App" - going away as soon as he recompiled with
a different Array-check.

So I would still classify the Not Not approach as "not really recommendable"...

Olaf