Automated Table

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have 2 tables: 'age' being the primary key to both.
1 table containts 2 fields which is automated to the the age e.g. (l 18 l
15.05235 l 35.5261) the second 2 columns contains values which are attached
to the the first column (in this case 18). How do i automate the 2nd table so
that it automatically inserts the values of field 2 and 3 above into the
relevant field of the 2nd table.

I need to no how do this step by step pls.
Thx
 
Not sure I understand the data. Which bit of this is the automated age?

l 18 l 15.05235 l 35.5261

And how does it get calculated?

As a general rule you do not store any calculated values.
 
I have 2 tables: 'age' being the primary key to both.
1 table containts 2 fields which is automated to the the age e.g. (l 18 l
15.05235 l 35.5261) the second 2 columns contains values which are attached
to the the first column (in this case 18). How do i automate the 2nd table so
that it automatically inserts the values of field 2 and 3 above into the
relevant field of the 2nd table.

I need to no how do this step by step pls.
Thx
Click to expand...

WHOA.

You have several major problems here, I fear.

Having two tables with the same Primary Key is *rarely* necessary. If
you're not familiar with the concepts of "Subclassing" or "Table level
security", then you're probably not making the right choice in setting
up such a one to one relationship.

If the Age is actually a person's age, it should probably not exist in
your table AT ALL; instead you should store the person's date of birth
and calculate the age dynamically.

And if you are assuming that having a relationship means that data
will be automagically copied from one table, to be stored redundantly
in a second table, you're mistaken. Data should not be stored
redundantly AT ALL, without a very good reason (which will usually be
that it is in fact NOT redundant). If you have fields 1 and 2 in
Table1, then they should only BE in Table1, and should be looked up
when needed using a Query.

Could you step back a bit and explain the purpose of these tables?
What Entity - real-life thing, person, or event - is each table
designed to represent? How are the entities for these two tables
related in the real world?

John W. Vinson[MVP]
 
Back
Top