Google " database schema examples BOM" and you will find many hits that will cover the topic
An example link is to SqlMag.com: Recursive Relationships A BOM is a hierarchical structure that describes relationships among components. For example, a car is made up of components such as a steering wheel Caution: This topic is probably too deep for your program, Sarah, as it tackles recursive many-to-many relationships. http://www.sqlmag.com/Article/ArticleID/42520/sql_server_42520.html ( yipee >> DOWNLOAD THE CODE: Download the Code 42520.zip) A better source to start may be: http://www.databaseanswers.org/data_models/ Hope this helps Jim Ault Las Vegas On 1/7/09 8:08 PM, "mfstuart" <[email protected]> wrote: > > Hi Sarah, > How familiar are you with the concept of Bill of Materials, Production > Orders, etc.? > Where a sellable (or shippable item) is made up of components, and the > components are assembled to gether with many other items - either purchased > or sub-assemblies. > This is the Bill of Materials - the structure of an item. > > When a customer order is processed, the manufacturing dept produces the > Production Orders, which looks at the B.O.M. and produces the Manufacturing > B.O.M. - this is an expanded production order with all the customer orders > multiplied against the B.O.M., which the assembly plant knows how many to > make. > > There are books on this on how to define the tables that hold the data, but > I'm sure you could find this info online. It's reasonably elementary. > > If you need more help, let me know. :) > > Regards, > Mark Stuart > > > Sarah Reichelt-2 wrote: >> >> Hi All, >> >> I'm setting up an SQLite database and having some problems with table >> design. The app is inventory control with a "Make" function i.e. it >> stores the quantities of each raw material you have and when you >> "make" a specified amount of a certain product, those amounts are >> automatically deducted from the raw material stocks. >> >> I have a very simple table for the raw materials, but the products >> table is not so obvious (at least not to me), mainly because each >> product will have a different number of items used in it's >> manufacture. >> >> Do I have to set up a large table allowing for the maximum possible >> number of items? >> e.g. >> product name >> product id >> item 1 >> quantity 1 >> item 2 >> quantity 2 >> . >> . >> . >> item 50 >> quantity 50 >> >> or is there any better way to hold a variable number of repeating fields? >> >> TIA, >> Sarah >> _______________________________________________ >> use-revolution mailing list >> [email protected] >> Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >> http://lists.runrev.com/mailman/listinfo/use-revolution >> >> _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
