I agree with ousoonerjoe in pretty much every aspect. As long as you are not doing something like this:
Code:
If something = false Then
Else
End If
You should be okay. Evaluating like the above is bad because you have to do a boolean check AND a comparison check. The comparison check is not necessary in this case.
While evaluating for True is easier to read, I am not sure that using the Not True check will be any worse as far as performance goes as long as you are not evaluating millions of records at a time.
In my opinion, the processing time necessary to negate a False to True should not impact your performance at all unless you are hammering through a lot of records....
=======================================
People think it must be fun to be a super genius, but they don't realize how hard it is to put up with all the idiots in the world. (Calvin from Calvin And Hobbs)
Robert L. Johnson III
CCNA, CCDA, MCSA, CNA, Net+, A+, CHDP
VB.NET Programmer