Need more information on your Database table design.
The following tables (from your explanation) are:
OfficePhoneTbl: defines 250 locations.
OfficeIDPK [Primary Key: numeric and sequential]
OfficeLocation [textfield, defining location, bldg number,etc]
1 Bldg 5
2 Bldg 6
PhoneLinesTbl: defines the phone lines, only;
LineIDPK [Primary Key: numeric and sequential]
LineDesc [textfield, description of line;
1 Voice Line
2 Data Line, T1
OfficeLineTbl: a Joining of the OfficePhoneTbl and PhoneLinesTbl. This table allows for anyoffice to have more than one phone line per office and easy to maintain. Queries are run against this table with the
OfficeLineIDPK [Primary Key: numeric, unique and sequential]
LineIDPK_FK [ForeignKey: Primary key of PhoneLinesTbl allows dupicate values in this case 70 lines per office.]
OfficeIDPK_FK [Foreign Key: Primary key of OfficePhoneTbl is the foreign Key in this table.Defines which line is at this office.]
OfficeLineIDPK LineIDPK_FK OfficeIDPK_FK
1 1 1
2 1 2
3 2 2
4 2 1
For the equipment, not sure what your database is defining equipment, however I would define it in its on table as the Office table and Line table, then establish the relationships...meaning if the equipment is a phonebox, you will have more than one line per phone box and I would imagine you would need the status of that line in that phonebox at a office building.
If you have any further questions, email me.
Hope this helps.