Your 2nd CASE was satisfied so no further CASE conditions were tested. Unlike some other languages, once a CASE condition is met, no other CASE conditions are tested.
John Israel Senior Programmer/Analyst Dayton Superior Corporation 1125 Byers Road Miamisburg, OHÂ 45342 -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of John Thompson Sent: Friday, August 05, 2011 10:58 AM To: U2 Users List Subject: [U2] Strange CASE Statement behavior I'm running on Universe 10.3.4 on AIX 5.3 on a PICK flavor account. I ran into some really weird behavior with a CASE statement this morning, or at least what I deem to be strange. I won't post the entire program... yet.... Basically I have some boolean variables that get set earlier in the program to the following values. exact_alpha1_found = @FALSE partial_alpha1s_found = @TRUE partial_names_found = @TRUE Then the CASE statement does its checks... BEGIN CASE CASE exact_alpha1_found ...do something... CASE (partial_alpha1s_found AND partial_names_found) ...do something... CASE partial_names_found ...do something... END CASE However, the CASE partial_names_found never executes. It fails!!! Is it only allowed to check these once, and thats it? In the debugger the value of partial_names_found is still a 1, even after the check fails. -- John Thompson _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
