|
I'm going to confess here that this is why I even add a little redundancy sometimes to my SELECT...WHEN... statements. That is, When Useflag = '0' and Nbr1 = 123 ...code... When Useflag = '0' and Nbr1 <> 123 ...code... instead of When Useflag = '0' and Nbr1 = 123 ...code... When Useflag = '0' ...code... Which will do the same thing, expecially when there is lots of code in between. (But not all the time). Is that OK with youse guys? Or am I violating some sacred principle of programming here? --Alan +++++++++++ ----- Original Message ----- From: <rob@dekko.com> To: <rpg400-l@midrange.com> Sent: Tuesday, July 30, 2002 5:26 PM Subject: RE: First Free Format > I am kind of curious too. It's gotten to the point where I avoid the IF > statement and use a SELECT. Even for a simple one option. > > It really makes you think. > > For example, all of you people who use system(). Instead of using > if ErrorFlag<>0; > > you instead > Select > When ErrorFlag=0; > ... > When ErrorCPF=CPF....; > ... > Other; > EndSl; > > It just make you try to cover your bases better. > > Rob Berendt > -- > "They that can give up essential liberty to obtain a little temporary > safety deserve neither liberty nor safety." > Benjamin Franklin >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.