Thanks for all the help, I learned a lot reading those documents.

I have two more questions the second of which depends on the answer to the
first.

1. The smaller I can keep the file size the better. So for fields such as
STREET (where each can show up on multiple entries and many entries can have
two STREET listings), would it be better to have a separate table holding
those and then link that to the LOCATION table or just have it stored
directly in the LOCATION table?

2. Many entries in the LOCATION table can have two STREET entries (listed
as Primary & Secondary). If STREET should be stored in its own table to help
reduce file size, how do I link the same table to two different entities
(Primary & Secondary) on the LOCATION table?

Example: (Field A_Entry - Field B_Entry - Field C_Entry)
Valve_1 - Primary_A Street - Secondary_B Street
Valve_2 - Primary_A Street - Secondary_C Street
Valve_3 - Primary_C Street - Secondary_A Street

Thanks again in advance.
--
"Imagination is more important than Knowledge. Knowledge is limited,
Imagination encircles the world." ~Albert Einstein