"freddy" wrote in message
...
I am a desktop support person and I have a vbscript to inventory all the
computers on the network. I use the script to gather information like
username, memory, hard drive space, and I am thinking about getting
installed
software. I have the script writing to an excel file, which is ok for now.
I
would like to use Access 2003 but my problem is the design. Do I create
one
table and have a field for username, computer name, memory, and so on or
do I
create more than one table like for username and one for computername.
Plus
how do I handle the installed software?
My idea was to have three tables: one for username which will have full
name, one for computername which will have all the computer stuff like
memory, hd, etc and one for software which will have software name,
version,
installed date, etc. Please someone help me out.

Thanks
Freddt

Think about entities with attributes and try to model them with your tables.
For example, can a user have more than one computer? If so then you need a
table for user (attributes: name, department, etc) and one for computers
(attributes: asset number, make, model etc) and there will be a one-to-many
relationship between them.

If a computer can have many users then there may be a many to many
relationship. That's the kind of thing you need to establish first because
your tables are the foundation of your app.

Keith.
www.keithwilby.co.uk