Planning a Database, Help Please

[Wally Steadman]

Greetings all,
I am planning a Database that will track different computers in different
buildings at different sites.

I was thinking, I need to set it up with Three Tables.

tblSITE
SiteID - Autonumber (PK)
SiteName - Text

tblBuilding
BldgID - Autonumber (PK)
SiteID - Number (FK) (Many side of a 1 - M with the tblSite)
Subnet - Text (will be a place to put the specific subnet number like
10.1.1.0)
SubMask - Text (Will be a default of 255.255.255.0 but they can edit it)

tblMachine
MachineID - Autonumber (PK)
BldgID - Number (FK) (Will be the many side of a 1 - M with tblBldg)
MachineName = Text (uses the machine name for ID purposes)
IPAddress - Text (will be the specific IP address such as 10.1.1.12)
MachineType - Text (Used to identify if machine is a router, switch, PC
etc.....)
Remarks - Memo (Used for information about specific machine in note type
form)

Am I making too many fields? Do I need to have the SiteID field in the
tblMachine also?

Am I going in the right direction? Thanks in advance

Wally Steadman
ICQ 11904383

 

[Jeff Boyce]

Wally

Looks like a reasonable collection of data, and since your Building table
points back to Site, you wouldn't have to have SiteID in the Machine table.

I would look at the MachineType field, however. Instead of using text
there, you could have another table (tlkpMachineType) with an ID PK, and use
the ID # here.

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Wally Steadman]

thanks Jeff,
Appreciate the reply. Yeah I was going to build a type table as well so
that there are limited choices so thanks, I know I am headed in the right
direction