G
Guest
What I need to do:
I have some rather expensive inventory items that I need to keep track of.
These are to be used in several projects (jobs).
I'm trying to design a simple database to help me keep track of where
everything goes, so I can bill the right job for the right products.
More Details:
Inventory items have an ID, and description. I need to know how many of each
item I still have remaining.
Jobs have unique ID numbers (I dont want to use autonumber for this).
I was thinking maybe I could design something that would sort of do
transactions.
Assign a transaction ID (Autonumber is ok), A date, a project # (job#)
and how many of each of the inventory items were transfered on that date, or
transaction.
I did a little designing, and came up with three tables.
Inventory
|_ ID
|_ Description
|_ Quatntity on hand (??)
Jobs
|_ ID
|_ Address
Transactions
|_ ID (autonumber ok)
|_ Date
|_ Quantity
|_ Description
Can someone suggest an efficient relationships model to make this work?
Thanks in advance
I have some rather expensive inventory items that I need to keep track of.
These are to be used in several projects (jobs).
I'm trying to design a simple database to help me keep track of where
everything goes, so I can bill the right job for the right products.
More Details:
Inventory items have an ID, and description. I need to know how many of each
item I still have remaining.
Jobs have unique ID numbers (I dont want to use autonumber for this).
I was thinking maybe I could design something that would sort of do
transactions.
Assign a transaction ID (Autonumber is ok), A date, a project # (job#)
and how many of each of the inventory items were transfered on that date, or
transaction.
I did a little designing, and came up with three tables.
Inventory
|_ ID
|_ Description
|_ Quatntity on hand (??)
Jobs
|_ ID
|_ Address
Transactions
|_ ID (autonumber ok)
|_ Date
|_ Quantity
|_ Description
Can someone suggest an efficient relationships model to make this work?
Thanks in advance