Any duplicate key (including the third duplicate record) would not set on L1
so that would be the "else" condition and would print a  line or am I
missing some elemental issue here?. 
 
---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
 
-------Original Message-------
 
From: Midrange Systems Technical Discussion
Date: 1/8/2004 11:55:49 AM
To: Midrange Systems Technical Discussion
Subject: RE: Using SQL to check for duplicate records
 
Booth,
Wouldn't three be more than 2?  Your original program didn't handle that
case very well.
 
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/08/2004 12:06 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
 
 
 
 
 
 
Isn't that exactly the point?  Aren't we looking for all records with more
than one record per key?
 
 
---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
 
-------Original Message-------
 
From: Midrange Systems Technical Discussion
Date: 1/8/2004 7:07:15 AM
To: Midrange Systems Technical Discussion
Subject: RE: Using SQL to check for duplicate records
 
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)
_______________________________________________

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.