Design

[Guest]

I have been trying to design a db for simple stock controll for a housing
assoc. I want users to be able to select repair materials from a list and
the quantities required for each repair. I then want users to click a
button and the system to be able to print out where to collect each material
(ie from store or from supplier) the problem is I do not know how to
correctly model the materials? I have thought of tables such as:
([tbl IssueOrder]{IO_ID, IODate})
([tbleIssueOrderDetails]{IODetailID, IO_ID, ProductID, QtyRequired})

which are linked as 1 tblIssueOrder has many tblIssueOrderDetails

and a products table as:
([tblProducts]{ProductID, ProducName})

but the problem is when the user clicks my check materials button, what
tables should I have? I was thinking of an aquisition table that will hold
details of materials as they come in and a 'goods out' to show materials
used, but what about units on order, would it be appropeiate to hold a third
set of tables for this or are there more conventional ways to model this
problem.

Any advice or comments would be much appreciated.

Thank you

 

[Dodo]

I have been trying to design a db for simple stock controll for a
housing assoc.

Anything you could use here?

http://office.microsoft.com/en-us/templates/CT011366681033.aspx