using queries instead of tables for forms

[Guest]

had massive cross information is several tables wanted to use more than one
table for aform creation , which when certain information is entered on one
form it auto enter that information on other forms(each person has 8
diffenerntform and needs all , soif I enter in on the first form "general
Information, it would auto create a form for that person on the"leave taken"
form.
was advised...here to use queries... notused to those...went and created
blank form to test it in properties instead of using table said use query
created query by dragging information from two diffent tables. looked good,
then went to design view on the form the field list came up wih all of the
fields that I had placed in my query. drug the fields onto the form arranged
them. then saved form , went back to preview View, all thatI could see was
the back ground, no fields , what am I doing wrong?

 

[John Vinson]

had massive cross information is several tables wanted to use more than one
table for aform creation , which when certain information is entered on one
form it auto enter that information on other forms(each person has 8
diffenerntform and needs all , soif I enter in on the first form "general
Information, it would auto create a form for that person on the"leave taken"
form.
was advised...here to use queries... notused to those...went and created
blank form to test it in properties instead of using table said use query
created query by dragging information from two diffent tables. looked good,
then went to design view on the form the field list came up wih all of the
fields that I had placed in my query. drug the fields onto the form arranged
them. then saved form , went back to preview View, all thatI could see was
the back ground, no fields , what am I doing wrong?

Trying to create a massive Master Query That Does Everything is going
too far. Yes, queries are vitally important - but that's not how they
should be used!

You should store the person's information ONLY in the People table. It
should not be stored redundantly in any other tables; all you need in
the "leave taken" table is the unique PersonID.

The most convenient way to enter data into such systems is to use a
Form (for the "one" side table) with Subforms (one subform for each
"many" side table). You can put subforms on the pages of a Tab Control
if you have problems with screen space. Popping up *separate forms*
can be done, but it's a lot more complex than using Subforms.

John W. Vinson[MVP]