The physical file does not have duplicates.  This is definitely an SQL
result set "work file" problem.  There are no joins, it even returns two
records on a count(*) select.  We have found dozens of SQL based PTF's (on
top of PTF's) that we are going to try, but it is pretty darn scary that
something like this can happen.  It's almost like dealing with Microsoft...
Yikes!

john

> -----Original Message-----
> From: Danny.Jahr@lawson.com [mailto:Danny.Jahr@lawson.com]
> Sent: Friday, July 09, 1999 1:46 PM
> To: MIDRANGE-L@midrange.com
> Subject: Re: SQL on 4.3 doubling up result set.
>
>
>
>
> This is from the DB team at SupportLine in Rochester.  Maybe
> it will help, maybe
> not.
> You can find more info at:
>
>
> http://as400service.rochester.ibm.com/supporthome.nsf/home/Sof
> tware+Knowledge+Base
>
> The most common cause of a query returning duplicate records
> is that there is
> more than one record in the
> secondary file that matches the comparison test. The proof is
> to query only the
> secondary file using the
> same selection criteria as the join. You will probably
> receive duplicate records
>  indicating that the file does
> have duplicate records that match the selection criteria.
>
> To determine the number of records that query joins when you
> have duplicates,
> multiply the number of
> records from each file involved in the join operation. For
> example, if the first
>  file has 2 records, the second
> file has 3, and the third file has 4, the join operation
> would return 24 records
>  (2*3*4).
>
> Change the join comparison test so that the selection is more
> descriptive and
> results in a record-to-record
> match. Or, use record selection criteria against the records
> to select the
> desired records from the result set.
>
>
>
>
>
>
>
>
>
>
>
> "John Bussert" <jbussert@stecnet.com> on 07/09/99 09:43:43 AM
>
> Please respond to MIDRANGE-L@midrange.com
>
>
>
>
>
>
>
>
>
>
>
>  To:      "MIDRANGE-L (E-mail)" <MIDRANGE-L@midrange.com>
>
>  cc:      (bcc: Danny Jahr/Lawson)
>
>
>
>  Subject: SQL on 4.3 doubling up result set.
>
>
>
>
>
>
>
>
> Has anyone had trouble with V4R3 and SQl?  I have a client
> that is having
> the result set returned twice.  Even a count(*) returns two
> count records.
> This is happening on interactive and embedded sql operations.
>  However,
> Query seems to be OK (very strange).  This is a new 730 with
> 4.3 that just
> went in over the weekend.
>
> Any assistance would be greatly appreciated.
>
> Thanks
>
> john
>
> John Bussert
> jbussert@stecnet.com
> Swift Technologies, Inc.
> 847-289-8339
> 847-289-8939 fax
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
>
>
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


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-2019 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].