Printable View
Look at the following code
VB Code:
The first two IF statements validate. However, the last one does not. Why is it doing that? Isn't that how AND is suppose to work?
Ok so I've isolated the problem quickly to something that is sooo stupid, who ever programmed it should be shot.
If 35 And 65 Then MsgBox "TEST" -> validates
If 37 And 65 Then MsgBox "TEST" -> validates
If you noticed, the AND statement validates WHEN both integers are odd or both are even :S. WHAT THE HELL IS THAT ABOUT? I didn't even know any language does such a useless validation :S.
VB isn't doing anything wrong. You are.Quote:
Originally Posted by INF3RN0666
'And' performs a bit-comparison of two numbers. to use your examples:what are you trying to achieve?Code:1000001 - 65 in binary
0100100 - 36 in binary
-------
0000000 - if both bits are 1 we'll get a 1 in the resulting bit position else we get a 0
the above comes out as 0 which is False
1000001 - 65 in binary
0100101 - 37 in binary
-------
0000001 - the result is 1, which is Not False and hence True
VB Code:
Try this:
VB Code:
OHHH bit comparison. I thought it evaluated each term on its own to 1 or 0, then it compared both. DAMN! I was doing InStr in a function and I usually put InStr > 0 but I realized that it should work either way. Now I understand why to put > 0. Thx for your help.
well you can use a single InStr on it's own like that:but once you introduce multiple terms with And / Or / etc. then each part needs to be a Boolean, otherwise you won't get the right results.VB Code:
Errr to what variable are you comparing the values against? Those statements will always return True.
EDIT: Or try bushmobile's suggestion