On Thu, Apr 10, 2014 at 4:57 PM, Mike Copeland <[email protected]> wrote:
> Opinion time... (or maybe it's a solid fact and I missed the memo?) > > Back in DBF days, when I had a file, for example "inventory" that would > have ongoing additions, I would have two (or more) tables: > Table 1: On-hand inventory available to sell (i.e., "onhand") > Table 2: Inventory that was sold (i.e., "sold") > Obviously, when something was sold, the record would be 'moved' from Table > 1 to Table 2 by reading it from 1, writing it to 2, then deleting it from 1. > ------------- Why combine Items with consumption of them? Inventory: defines the item, has a key to reference said item OrderLinenItems : defines consumption of all items, and references InventoryID to get description of item. PurchaseItems: Defines restocking of items using same InventoryID to get description of item. Should you place the quantity Onhand in the inventory table or do you just show the difference between all purchased - all sold? I know it gets fun when an order has been placed but not shipped. Isn't that why we make the mediocre money? -- Stephen Russell Sr. Analyst Ring Container Technology Oakland TN 901.246-0159 cell --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CAJidMYJk8GtSVq9UXuLj=ijbai_gwvb18-yavpftsfzzvxs...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
