Pat and Bob,
Over the last couple of days I've been somewhat consumed with figuring out the normalized table structure for my database. I feel that I've come a long way since I started this post and would appreciate it if you could take a quick look at my attached table relationships and let...
Pat,
Thanks for the feedback. I am beginning to understand the concept you are driving at, however I am not sure it's entirely applicable to my envisioned database.
What I am looking to do is store my corporate customer's wireless contract data (Corporate contract with AT&T Mobility...
Bob,
Thanks for the quick reply. I actualy have several "Many" tables linked to tblContractHeader. These tables are:
tblVoiceRates
tblDataRates
tblFeatureRates
Can I use a single junction table for all three of these or should I use a seperate junction table for each one?
Thanks,
Mike
Hello,
I have two tables that are linked in a one to many relationship:
tblContractHeader (One)
tblRatePlans (Many)
These two tables are linked via ContractID which is set to Autnumber in the tblContractHeader table and Number in the tblRatePlans.
I have a form set up to populate the...
Perhaps I will get more feedback if I better explain the purpose of my database:
I am looking to store data on my Customer's Wireless Telecom contracts:
The ContractHeader Table will capture all the high level contract information including Customer Name from the Customer Table, Vendor Name...
Hello,
I am creating a database for work to store telecom contract rates for my customers. The two core functions of my database are to endable end users(myself and my team members) to input new contracts and their associated rates and then run ad-hoc reports as needed.
I established what I...