Please suggest relationships model

So, since all you can do is make worthless responses that do not help the OP
one iota, you must not have any intelligence at all. And since you imply
that Moe is an amateur, you have no couth either!

"John Marshall, MVP" wrote in message
...
Still thick as a brick.

These newgroups are for FREE peer to peer support.

The only thing worse than an amatuer create his own database is to have
the amatuer helped by steve at a "reasonable fee".

This stuff is not rocket science and most reasonably intelligent people
can create an adequate solution.

John... Visio MVP

"Steve" wrote in message
ink.net...
Yes, Access is the preferred choice! You can start with the tables I
suggested, modify fields to suit and build from there. If you get stuck,
you can post questions to the newsgroup.

I offered my help if you wanted to get your database up and running as
quick and painless as possible.

PC Datasheet
Providing Customers A Resource For Help With Access, Excel And Word
Applications






"Moe" wrote in message
...
I was kind of hoping not to have to purchase any software for this...
Excel could do the job, but an access database would be so much better
organized.



--
Moe


"Steve" wrote:

I have assumed that your inventory items are consumable and
periodically you
purchase items to replenish your inventory.

TblJob
JobID
JobNumber
JobDescription
Job Address fields

TblItem
ItemID
ItemDesc
QuantityOnHand

TblItemToJob
ItemToJobID
JobID
ItemToJobDate

TblJobItem
JobItemID
ItemToJobID
ItemID
Quantity
JobItemAssignedCost

TblItemVendor
ItemVendorID
VendorName
Vendor contact fields

TblVendorItem
VendorItemID
ItemVendorID
ItemID
ItemCost

TblItemPurchase
ItemPurchaseID
ItemVendorID
PurchaseDate
PurchaseOrderNumber

TblItemPurchaseDetail
ItemPurchaseDetailID
ItemPurchaseID
ItemID
Quantity
UnitCost

If you need help, I can help you for a very reasonable fee. Contact me
at my
email address below.

PC Datasheet
Providing Customers A Resource For Help With Access, Excel And Word
Applications






"Moe" wrote in message
...
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

--
Moe