How do you autofill from one table to fill another one?

[Angie]

I'm trying to enter in Federal Tags, and i need the description to fill in as
well...ex. the tag is K 050 and then the description is a sentence about what
the tag is about...is there a way to fill it in?

Also, I'm trying to do facilities and have it linked to what state the
facility is in. Such as ABC is in Iowa.

I have the two tables set up independently from the Main table...I just
can't figure it out after that...

 

[John W. Vinson]

I'm trying to enter in Federal Tags, and i need the description to fill in as
well...ex. the tag is K 050 and then the description is a sentence about what
the tag is about...is there a way to fill it in?

Also, I'm trying to do facilities and have it linked to what state the
facility is in. Such as ABC is in Iowa.

I have the two tables set up independently from the Main table...I just
can't figure it out after that...

You don't.

Relational databases use the "Grandmother's Pantry Principle": "A place - ONE
place! - for everything, everything in its place".

You need a Tags table with a field for the tag and a description field. Your
table should have a tag field; if you need to see the description, use a Query
joining the two tables on the Tag, and display the description from the tags
table. It is neither necessary nor good practice to store the description
redundantly in a second table.

If you're entering data directly in table datasheets... don't! Use a Form
instead. On the Form you can use combo boxes (based on the Tags table or the
Facilities table) to store one value while displaying another.

John W. Vinson [MVP]

 

[Angie]

You don't.

Relational databases use the "Grandmother's Pantry Principle": "A place - ONE
place! - for everything, everything in its place".

You need a Tags table with a field for the tag and a description field. Your
table should have a tag field; if you need to see the description, use a Query
joining the two tables on the Tag, and display the description from the tags
table. It is neither necessary nor good practice to store the description
redundantly in a second table.

If you're entering data directly in table datasheets... don't! Use a Form
instead. On the Form you can use combo boxes (based on the Tags table or the
Facilities table) to store one value while displaying another.

John W. Vinson [MVP]

I guess I'm getting a little confused. I do have a form set up...along with
the two tables. How do I have it so if I fill the tag number (say, K 050)
into the form, it pops up with the description and places it in the Main
Table?

Sorry!

Angie

 

[John W. Vinson]

I guess I'm getting a little confused. I do have a form set up...along with
the two tables. How do I have it so if I fill the tag number (say, K 050)
into the form, it pops up with the description and places it in the Main
Table?

No.

There should not *BE* a field Description in the main table. It should simply
NOT EXIST. It's redundant and it's not necessary!

You can *display* the description (from the Tags table) on the form if you
wish, but it is neither necessary, nor beneficial, nor correct to store the
description into the main table.

John W. Vinson [MVP]