Re: Please suggest relationships model

Do-it-yourself is not always the best decision. In fact, it can be a very
poor decision. Yes, from only the database point of view, if you create a
database and it works for you, do it yourself is cheapest. From a business
perspective, it can be much more expensive than hiring someone to build the
database for you. The do-it-yourself route requires dedicated time and
effort which means taking the time and effort away from something else. If
you could have spent that time in a more profitable way such as increasing
sales, the database cost you the value of the lost sales and that could
easily be many times the fees you would have paid someone to create the
database for you.

PC Data***
Providing Customers A Resource For Help With Access, Excel And Word
Applications
resource@xxxxxxxxxxxxxxx





"Gina Whipp" <NotInterested@xxxxxxxxxxxxx> wrote in message
news:O2f793I0HHA.1164@xxxxxxxxxxxxxxxxxxxxxxx
Moe,

Below is a few links to help you get started... Please note, this FREE
newsgroup provided by Microsoft would NEVER dream of charging you.
Everyone (well almost everyone) VOLUNTEERS their time to provide FREE
support and assistance.

Ms Access Fundamentals: http://www.functionx.com/access/

Samples downloads: http://www.rogersaccesslibrary.com/TableOfContents3.asp

Code, sample downloads, sample coding (I love this site):
http://www.mvps.org/access/

Data model samples: http://www.databasedev.co.uk/data_models.html

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

"Moe" <henriquezmoi@xxxxxxxxxxx> wrote in message
news:4741BC76-878E-49A2-9FAA-9AF95E42F1F8@xxxxxxxxxxxxxxxx
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




.