RE: Using SQL to check for duplicate records

I am not sure look ahead fields are still supported in RPGIV.  In any event,
what would a look ahead field gain for you?  The cycle works just fine. 
Print a line anytime L1 is not on.  Its really that simple.  There's no need
for anything fancier. 
 
 
 
---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
 
-------Original Message-------
 
From: Midrange Systems Technical Discussion
Date: 1/8/2004 9:49:18 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Using SQL to check for duplicate records
 
Hmmm... _IF_ I were doing it in RPG, I might define the L1 field (L1FLD) and
then define the same record positions as a lookahead field (LAFLD). At
L1-detail time, I'd seton an indicator if L1FLD = LAFLD. The indicator would
be setof at L1-total time. Output would be printed at detail time as long as
the test indicator was on. It should be on for every record in the L1-group
if there any duplicates and off if no duplicates.
 
But I've never done it, so don't know if it'd work. I'd probably go with
whatever SQL seemed to work well (to keep it from being a pure RPG post and
needing to be sent to different list.)
 
Tom Liotta