One to one tables

[Troy W.]

Ok so I could use some help on table design. I am building a database that
tracks among other things "devices" on my network. A device could be a
computer, printer, IP phone, etc. For each type of device there are
obviously different types of information such as phone type and phone number
for an IP phone and computer model, computer name, etc for a computer. My
question is this: How is the best way to do this?

My first impression is to do a device table for general information
applicable to all "devices" and it has a one to one relationship with a
"computer" table and a "IP phone" table. Is this the best way to do it, or
make a single table that contains all of the details for every type of device?

Assuming it is multiple one to one tables, I am guessing that for the form
source, I would simply make a query that links the applicable tables
together? I appreciate your guys help.

Troy W.

 

[June7]

It all depends on how many items you have and how many of each type and
how much detail you need to track. Your needs could be accommodated by a
simple spreadsheet or a full-blown database. Do you need to track CPU's
and monitors as a unit or individually, do you have 50 iPods with
different features(memory) and accessories, do you care about the
accessories or just expense them, etc.? The more detail the more
different items. Detail could be so specific that you essentially end
with each and every item being unique. Have you looked at the MS
tutorial that uses a template database called Northwind? I think it is
an inventory database. Perhaps you will find it helpful. Otherwise, by
your posting I think you have a grasp of the concepts.