The information is still contained in those tables (tblDuctbank and tblCircuits). The only important information contained in each table is for tblCircuits the ductbanks numbers and for tblDuctbank the circuit numbers.
+Ductbank ID Ductbank CIRCUIT 1 CIRCUIT 2
Ductbank 5 4DB08C1...
I started organizing the data like in the last post, this is an example of what I did.
DCID Circuit ID Ductbank ID
10 Circuit 1 Ductbank 284
11 Circuit 1 Ductbank 204
12 Circuit 1 Ductbank 130
13 Circuit 1 Ductbank 62
I had to manually go through and enter each circuit 1 under each ductbank...
As it is, each circuit has one record in tblCircuit and each duct has one record in tblDuct. The other information contained in the other fields is the information that I'm trying to correspond to. It would be very labor intensive to organize each case of one circuit and one ductbank, unless...
Alright, so I've got my CircuitID and DuctbankID and their corresponding tables set up. I'm not sure how to create the tblConnection with the common fields.
example where RWY is the ductbank primary key in the Duct to Circuit table.
RWY CIRCUIT 1 CIRCUIT 2
4DB19B4...
Thanks, I am new to access. I'll look into the normalization but the many to many relationship is exactly what I am talking about. I'll let you know when I come to a roadblock.
I have two tables, one contains all of the circuits and then each individual circuit shows all of the related ductbank in the next column. The other table is the opposite, it contains all of the ductbank in the first column and the second column contains all of the ductbank that it goes...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.