|
Your assumption is that VALUES and RANGE only allow for literals--not fields. I wouldn't assume that myself. -Bob Cozzi www.iSeriesTV.com iPod your industry news instead of reading it. Coming June 2006 Ask your friends to tune into iSeriesTV.com -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx Sent: Friday, May 26, 2006 10:45 AM To: RPG programming on the AS400 / iSeries Subject: RE: RPG, 10 years from now Since WSU was a combination of RPG and Screen, don't we, in effect, have those opcodes? Aren't they just segregated out to the screen now (DDS)? VALUES might be useful for a limited selection like '0' or '1'. However for anything more than that I'd be a little leery of the potential for over hard coding. SQL gets around this with their IN statement IN(select code from codeTable) Now, if a VALUES is to perform different actions then we're back to the elseif versus select argument again anyway. Range or between would be pretty. Rob Berendt
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.