Jim, In general you are not putting the correct foreign key in the tables such that you can figure out where things are and to what they are connected. Just as a start I would put the UnitID in the PC (tower) table rather than BuildingID. Then in the Monitor and Periphials I would put the PCID from the tower table. and so on - - - When you write the add tables you will need a pull down list of the values you need for the foreign keys. For example in the form for adding PCs you will need a pull down for Unit. For the Monitor form you will need a pull down for the Tower(PC) and so on - - - Then when you set up form and reports to retrieve data you will base them on queries that have two (or more) table in them with equi-joins Dick
--- In [email protected], "luvmymelody" <[EMAIL PROTECTED]> wrote: > > Hello all, > > I am developing a database for computer inventory regarding several > departments in different buildings. There are 3 buildings and 10 > departments. There are several departments in one building and each > department has a computer. I have always struggled with the physical > model of designing a database. Can someone take a look at the table > structure and let me know if I am on the right track? I will > probably need to break out the peripherals to different tables also? > Thanks > Jim Wagner > > Building > BuildingID > BuildingName > Address > City > State > Zip > > > Unit > UnitID > UnitName > UnitNumber > UnitPhone > BuildingID > > > Monitor > MonitorID > Manufacturer > ModelNumber > SerialNumber > BuildingID > > > Tower > PCID > Manufacturer > ModelNumber > SerialNumber > CPUSpeed > CPUName > RAM > HardDiskSize > Description > BuildingID > > > Periphials > Mouse > Keyboard > Printer > Fax > BuildingID > > > Printer > PrinterID > Manufacturer > ModelNumber > SerialNumber > BuildingID > > > ProductKey > ProductKeyID > ProductKey > BuildingID > > > Registered Number > RegisteredID > RegistereNumber > BuildingID > > > Software > SoftwareID > Title > SoftwareDescription > Manufacturer > BuildingID >
