August 05, 2011 11:00 AM
>> To: U2 Users List
>> Subject: Re: [U2] Strange CASE Statement behavior
>>
>> Hi John
>>
>> Based on the values of your variables, your CASE construct is behaving
>> perfectly!
>>
>> As far as I can tell, the reason p
om: u2-users-boun...@listserver.u2ug.org
> [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Glenn Sallis
> Sent: Friday, August 05, 2011 11:00 AM
> To: U2 Users List
> Subject: Re: [U2] Strange CASE Statement behavior
>
> Hi John
>
> Based on the values of your variables, your CASE
This is the reason you always place CASE 1 at the end... :-)
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Glenn Sallis
Sent: Friday, August 05, 2011 11:00 AM
To: U2 Users List
Subject: Re: [U2] Strange CASE
Sorry, the fourth line of my email should read: "The subsequent
conditions"
Glenn
Am 05.08.2011 16:59, schrieb Glenn Sallis:
Hi John
Based on the values of your variables, your CASE construct is behaving
perfectly!
As far as I can tell, the reason partial_names_found never executes is
Hi John
Based on the values of your variables, your CASE construct is behaving
perfectly!
As far as I can tell, the reason partial_names_found never executes is
because the preceding clause in your CASE statement evaluates to /true/.
In a CASE block, each clause is checked until a clause is f
ehalf 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 thi
-
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 accoun
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 prog