looking fo jump start

J

jono

Hello,

I have been given the task to design a database for the ICT support team.
This should include an inventory of all computers\ hardware in each room;
when it was purchased; warranty; repair history and so on.
They also want me to keep track of printer stock levels as well.

I am eager to start this but simply have no idea what field should go in
what table for best results.

I was thinking that I should have one table as TblLOCATION and populate it
with all the rooms in our school.
Then I created another table called TblMain with the following headings:

model:make:description:location:warranty:datepurchased:history:colink:blckin
k:Toner:stock level:
I then created a one to many relationship between location and location.

I am not sure what the purpose of a primary key is so I set location in
TblLocation and Model in TblMain to PK.

Then I am wondering if it would be best to have separate tables for the
following:
blkink
colink
model

Sorry for such a long post. I would really appreciate any thoughts on how to
set my DB out.

Thanks in advance

jono
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top