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

midrange-l-request@xxxxxxxxxxxx wrote:

>   6. RE: Using SQL to check for duplicate records (rob@xxxxxxxxx)
>
>And when would you activate that, at control break time?  If so, then how
>would it know both the rrn of first duplicate, and the second duplicate?
>
>
>"Booth Martin" <Booth@xxxxxxxxxxxx>
>
>Yes.
>
>  FGCKFL3    IP   E       K DISK    INFDS(DB3) BLOCK(*NO)
>       *  ..................................................
>       * Get the record Number, to know which record to update/process:
>      D DB3             DS
>      D DB3RRN                397    400B 0
>
>-------Original Message-------
>
>Would that method display the RRN's of both duplicates?
>
>
>"Booth Martin" <Booth@xxxxxxxxxxxx>
>
>ahhhhh the joys of using RPG the way it was intended...
>
>Such an easy problem with an L1 break and using the  INFDS for the
>input/primary file.

-- 
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone  253-872-7788 x313
Fax    253-872-7904
http://www.powertech.com


__________________________________________________________________
Thank you for using Netscape.