RE: Subfile in SQL

Dane,
        Here is an example of some of the code I posted a while ago.
Its not a complete program but I believe it has most or all the bits
needed to do page at a time sub files.  

http://archive.midrange.com/rpg400-l/200409/msg00254.html

You biggest issue is going to be attempting to fulfill position to
requests.  In a SQL results set you cannot reference the data set by
value only by ordinal value.  I personally have not found a way around
this limitation and maintain code that is not very complex.   I also has
requirements to make the SQL cursor reflect current data (i.e., no
temporary table data that have to be recreated to get real time
changes). 

Thanks, Matt



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Dane Cox
Sent: Thursday, March 16, 2006 9:10 AM
To: RPG programming on the AS400 / iSeries
Subject: Subfile in SQL

Hi all,
 
I was searching the archives for single page subfile ideas and ran
across an old thread about using SQL in subfiles.  I was not able to
find any examples of anyone actually implementing any of the techniques
suggested unless I missed some threads.  I am particularly interested in
the single page techniques with page up, page down and position to.  I
am currently looking at a basic inquiry program, but wouldn't mind
seeing something involving maintenance (updates, adds, deletes) as well.
Has anyone ever implemented anything like this and if so would you care
to share that code?
 
I would also be interested in hearing any thoughts on performance as
well as thoughts on whether or not this is something worth diving into,
or should I just stick with the traditional method?   I am sure there
are opinions out there on both sides and I would appreciate hearing
them.
 
Best regards,
Dane
 



NOTICE: This electronic mail message and any files transmitted with it
are intended exclusively for the individual or entity to which it is
addressed. The message, together with any attachment, may contain
confidential and/or privileged information. Any unauthorized review,
use, printing, saving, copying, disclosure or distribution is strictly
prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.