By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,482 Members | 2,073 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,482 IT Pros & Developers. It's quick & easy.

Creating the correct type of table

P: 2
I need help to create a database for telecom circuits. Iím not sure of how to approach it. Hereís a brief description of what I need to create. Each circuit has a point A and a point B. The ports for each site would be either originate (ORG) or answer (ANS). The equipment used at point A and B is the same. For example, Site A Node, Card, Port (ORG) -- Site B Node, Card, Port (ANS). What would be the most efficient way to create table(s) for this? I've tried making one table with columns such as SiteA_Node, SiteA_Card, SiteA_port, SiteB_Node, SiteB_card, SiteB port. I've simplified it here, but when I made this I had something like 20 columns for Site A and 20 columns for site B. But this creates a huge table with basically duplicate columns. And the queries donít quite come out right. I've also tried creating a table like this: Site, Node, Card, Port, ORG/ANS; and just enter each end into its own row. But then I'm not sure how to combine the two rows to create an end-to-end circuit (which would be necessary for a report or display form), and make sure that I'm combining the correct data for Site A and Site B. Any help on this would be greatly appreciated. Thanks in advance.
Oct 14 '07 #1
Share this Question
Share on Google+
2 Replies


MMcCarthy
Expert Mod 10K+
P: 14,534
See if the following structure solves your problem. The assumption made is that no two Nodes are the same.

tblCircuit
CircuitID (Primary Key)
CircuitName
SiteANode (foreign key referencing primary key of tblNodes)
SiteBNode (foreign key referencing primary key of tblNodes)

tblNodes
Node (Primary Key)
Card
Port
ORG/ANS
Oct 14 '07 #2

P: 2
See if the following structure solves your problem. The assumption made is that no two Nodes are the same.

tblCircuit
CircuitID (Primary Key)
CircuitName
SiteANode (foreign key referencing primary key of tblNodes)
SiteBNode (foreign key referencing primary key of tblNodes)

tblNodes
Node (Primary Key)
Card
Port
ORG/ANS


Thanks, I'll try it. You're assumption is correct about no two nodes being the same.
Oct 14 '07 #3

Post your reply

Sign in to post your reply or Sign up for a free account.