× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



That might work, providing you didn't have more than 2 with the same key.

Rob Berendt
-- 
"All creatures will make merry... under pain of death."
-Ming the Merciless (Flash Gordon)




"Booth Martin" <Booth@xxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
01/07/2004 03:53 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
<midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
RE: Using SQL to check for duplicate records






something like this maybe? 

     FTest01P   IP   E           K DISK    INFDS(DB3) BLOCK(*NO)  
 
     FQPrint    O    F  132        Printer  
 
      *  ..................................................  
 
      * Get the record Number, to know which record to update/process:  
 
     D DB3             DS  
 
     D DB3RRN                397    400B 0  
 
  
 
     D SavedRRN                             Like(DB3RRN)  
 
 
**--------------------------------------------------------------------* 
     ITest01Rec  
 
     I                                          States        L1  
 
 
**====================================================================* 
      ** M A I N   C A L C U L A T I O N S 
* 
 
**====================================================================* 
  
 
     C                   If        *INL1  
 
     C                   eval      SavedRRN = DB3RRN  
 
     C                   else  
 
     C                   except    printline  
 
     C                   endif  
 
      *-----------------------------------------------*  
 
     OQPrint    E            printline   1  
 
     O                       States              20  
 
     O                       SavedRRN           + 2 
     O                       DB3RRN             + 2 
      *-----------------------------------------------* 
 
---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
 
-------Original Message-------
 
From: Midrange Systems Technical Discussion
Date: 1/7/2004 9:07:59 AM
To: Midrange Systems Technical Discussion
Subject: RE: Using SQL to check for duplicate records
 
Sample code?
 
Rob Berendt
--
"All creatures will make merry... under pain of death."
-Ming the Merciless (Flash Gordon)
 
 
 
 
"Booth Martin" <Booth@xxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
01/07/2004 09:21 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
 
 
To
<midrange-l@xxxxxxxxxxxx>
cc
 
Fax to
 
Subject
RE: Using SQL to check for duplicate records
 
At L1 time we would save it as a work field.  At non-L1 time we'd have a
duplicate and would print a line with the key and both RRN numbers.

---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.