Help designing db

J

jmuirman

I have designed some fairly advanced dbs using basically 1 main table and a
few look-up wizards. Now I'm trying to go back and learn how to use several
tables to replace my main table and having difficult getting the concepts.

My question is how to design where I want to have several benefit plans
attach to 1 person. I connected the DBs with a 1 to many relationship. But
when I try and enter data in a form - I can't populate the fields. I would
like to have a from that is populated by the annuitant data and then let's me
add several plans. I will also need to do some fairly significant
calculations with this data - for example, I will use the tables in a query
to calculate the annuitant's age, to calculate the date of firstpayment in
say x number of years. Here are my tables:

T-ANNUITANT T-BENEFIT
[AUTOID] [AUTOID]
[Annuitantfirst] [COST/1000]
[AnnuitantLast] [Benefit1]

[dob] [Mode]
[TaxRate] [Years]

I have other tables that I want to work with this data like a life
expectancy table - I want the Annuitant dob to automatically show a life
expectancy in years....

Thanks for your help.

John
 
J

Jeff Boyce

Why do you feel you must "use several tables to replace [your] main table"?
Without a better idea of your data, NOT your table(s), I'd be hard pressed
to offer suggestions.

From your post, it sounds like you have Persons and BenefitPlans as entities
about which you wish to keep data. I have a hunch there are others.

Consider stepping away from the computer and using paper/pencil to sketch
out the entities about which you will record data, the relationships among
the entities, and the attributes (data) you wish to store about each.

Feel free to check back here for reactions to your initial design ideas.

Then fire the PC back up and start designing tables.

Forms come afterwards!

Regards

Jeff Boyce
<Access MVP>
 
Top