View Single Post
  #5  
Old February 28th, 2006, 06:55 PM posted to microsoft.public.access.gettingstarted
external usenet poster
 
Posts: n/a
Default Database Design Process Questions

I'm going to get a little more advanced than the previous posters, but
it will be good to have the right database schema.

I'd start with a Computers table. List all the things that you need to
know, including OS Version, Memory available, Serial Number, etc.

Next, have a Periphials table. This will include everything like hard
drives, monitors, optical drives, scanners, printers, etc. This is a
one to many relationship with Computers

Next is a Software table. Include fields for version information,
number of licenses owned by the company, etc.

Finally, have a ComputerSoftware table. This will be a one-many
relationship with both the Computers table, and the Software table.
This will have a record for each installation of the software on a
computer.

Finally, once you build those, look into WMI
(http://msdn.microsoft.com/library/de..._reference.asp).
This will allow you to remotely ping the computer for all the
information that you need, saving you from going out to each of the
computers. You will need WMI enabled on your pc's, and be a domain
admin to run this. The advantage is that inventories are much easier
to do, and you can get alot of information about a computer this way,
including software installed.

If you need more help, I have some classes already created that do the
brunt of the work.

Chris Nebinger

Chris DOT Nebinger AT GMail DOT com