× 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.



It may be a good idea to define diferent "User Defined Types" for quantity order and shipped. In this way SQL can make sure you make your bill for the quantity sipped, and gives you an error if you try to bill the quantity ordered or if you substract it from your stock.

___________________________________________________________________________________________________
rob@xxxxxxxxx wrote:

Actually, as I sent it I wondered about that. Mostly the item number field.

Quantity ordered has a totally different meaning than quantity shipped. Generally, while none of their attributes may be the same, except for their size attributes, there is nothing that says their size attributes must match. Therefore I would argue that your reference file should have a separate field for quantity ordered and quantity shipped. That you want to cascade these down from a common "quantity" field is ok.

Perhaps this is were we need to start taking more advantage of DB2. For example on those multiple item number fields in the transaction file we should have referential constraints pointing back to the item master file. Then, either by displaying the constraints on the master file, or by using iSeries Navigator to draw a nice navigator, you can see all the places where item number is referenced.





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.