Relationship Question

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am attempting to design a database to store static IP addresses and
releated information. IP addresses are made up of 4 values (or octets, ie.
10.125.2.30). The combined IP address must be unique with some octets unique
to the location of a particular network for example:

Location 1 = 10.1.1.X
Location 2 = 10.1.2.X
Location 3 = 10.1.3.X etc.

with the first 3 octets being the Network value and the X being a variable
value.

The octet values have inherent limitations and so must be stored in seperate
fields so each value can be validated (i.e octet values cannot exceed 254.)
Other than the last value of the ip address (X) the values for each location
are the same. So I created a Location table...

Tbl_Locations:

Location
IPOctet1
IPOctet2
IPOctet3
IPOctet4
Subnet1
Subnet2
Subnet3
Subnet4

My second table is Tbl_IPData:

IPOctet4
Device
Location
HostName
etc...

As you can see I stored the last octet of variable data in the 2nd table.
I could store all the data in one table but then there are tons of redundant
information. But with two tables my problem is I have no unique value in my
Locations table to link to the IPData table. So...my goal is to combine the 3
octets of non-variable data with the one octet of variable data on a form. I
also want to populate certain fields based on the Location value in a combo
box . So... when entering a new IP Address you first select the location.
Based on the location I want the remaing static values to populate the form
(i.e the subnet and network values.)

I hope this makes sense. If you need clarification let me know.

Thank you very much in advance!!!

Tim
 
If your IP addresses are static, then I would assume that you have a limited
number of them. Couldn't you set up a table that just has all of those IP
addresses, and then reference them from your other table?
 
Tim

Are you planning ahead to IPV6?

Regards

Jeff Boyce
Microsoft Office/Access MVP
 
Yes, I could do that but having the data stored as one value greatly limits
the functionality.
 
Jeff, I really haven't given much thought to it although I would like to
incorporate IPV6 into the design. I'm not very familiar with the structure
other than it uses a pair of 64 bit addresses. Any suggestions on how to
proceed design wise? If it's not much more difficult I would like to have V4
and V6 capabilities.


Thanks!!!
 
Tim

I'm not familiar with the intricacies of IPv6, but I suspect you could
Google them fairly easily.

Regards

Jeff Boyce
Microsoft Office/Access MVP
 
Back
Top