Re: Embedded SQL For Screen Load

On Thu, Dec 15, 2016 at 2:56 PM, <MichaelQuigley@xxxxxxxxxx> wrote:

Really? What about the following?

where db_column >= :search

Lot's of posts over the years detailing the hoops needed in SQL to do a
position to (and provide the exact functionality you have now). Not

really

worth the effort IMO.

It's not the same.​ From a SETLL, you can read forward or backward. The
SQL above only allows forward.

If you want to allow seamless (to the user) forward or backward, you've got
hoops to jump through.

It can be done, but there's more effort for no benefit. Just leave it as
native I/O.

If you what to move to SQL, then move to SQL. Forget "Position to" and use
"Starts with" or "Contains" or whatever. Consider distinct sort by
functionality.

So instead of being able to simply position to a customer name, your user
can get a list of customers with State=TX ordered by Zip code for instance.

Charles
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD