Re: Using SQL to check for duplicate records

[rob@xxxxxxxxx]

True, anytime you had any consecutive, start dumping them out.

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:03 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






I am curious as to your reasoning for saving until L1 total time?
 
 
 
---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
 
-------Original Message-------
 
From: Midrange Systems Technical Discussion
Date: 1/7/2004 9:46:59 PM
To: Midrange Systems Technical Discussion
Subject: Re: Using SQL to check for duplicate records
 
Control break, another good idea.
 
I might prefer to store all the RRN's for each group into an
array, and at L1-total time print it the whole thing if
there is more than one (assuming a small number of values to
save, and small group of records.).
 
- Alan
_______________________________________________
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.