I think this whole exercise is based on the assumption that the customer number CustNbr is in the order header file OrderHeader but not the detail file OrderDetail, and that the item number ItemNbr is in the OrderDetail file but not the header file. But that the join must sort by CustNbr then ItemNbr. Shew.

Perfect database normalization in the real world! Wow! And no redundancy!

-Alan


If reading individual records, maybe native IO would be faster? (Assuming the 
key fields and common field are key fields in the component files. . .)




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2025 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.