RE: SETLL in SQL ?

["Wilt, Charles" <WiltC@xxxxxxxxxx>]

> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx 
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
> Sent: Thursday, October 11, 2007 2:36 PM
> To: 'RPG programming on the AS400 / iSeries'
> Subject: RE: SETLL in SQL ?
>
> <opinion>
> I think it's absolutely wrong for a programmer to tell the 
> user what features they can and cannot have because of an 
> artificial limitation imposed by programming.  It's the 
> programmer's job to provide EVERYTHING the user needs, but to 
> balance the price and performance.  If a user really needs 
> positioning capabilities, then it's the programmer's job to 
> give it to them, not to tell them they have to give up something else.
>
> Technology-driven decisions often aren't in the best 
> interests of the user.
> </opinion>

Joe,

I don't know about you, but I've yet to run across a business need for a "position to".

The business need, thus what the user really wants is a way to get to the part of the list they need.
The user may be used to "position to" but that doesn't mean you have to give it to them.  Particularly
when there's a better way.

Personally, I normally use "subset by" as it tends to be more productive for the user.

IMHO, if the user is paging forward or backward through many screens then there's probably room for
improvement.

Charles


This e-mail transmission contains information that is intended to be confidential and privileged.  If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful.  Please reply to the message immediately by informing the sender that the message was misdirected.  After replying, please delete and otherwise erase it and any attachments from your computer system.  Your assistance in correcting this error is appreciated.