Pushing Data

[Guest]

I have a table named Recruitment.

I have a form with a lookup designed in it to fill in 2 fields in the table
Recruitment. One field is RecruitmentNumber ie 2005-001. The second is
ClassificationTitle ie Chemistry Instructor.

Once selected in Lookup, I would like both fields in Recruitment to be
filled.

I have heard that the process is called pushing. But I have not found any
good examples or heard any good explanations.

Please help.

Thank you in advance!

 

[John Vinson]

I have a table named Recruitment.

I have a form with a lookup designed in it to fill in 2 fields in the table
Recruitment. One field is RecruitmentNumber ie 2005-001. The second is
ClassificationTitle ie Chemistry Instructor.

Once selected in Lookup, I would like both fields in Recruitment to be
filled.

I have heard that the process is called pushing. But I have not found any
good examples or heard any good explanations.

Please help.

Thank you in advance!

Posting your question four times won't get you a faster or better
answer.

I would suggest that the ClassificationTitls SHOULD NOT EXIST in
Recruitment, if it can be looked up as needed from the lookup table.
Could you explain why you need to store it (apparently redundantly) in
a second table?


John W. Vinson[MVP]

 

[Guest]

Hello John:
Thank you for replying. I do understand your point about redunds. The
reason it is necessary is to allow the user of the form to see their
selection. The recruitment table is viewed as a subform. The user makes the
selection and needs to see both the code and the class title.
Thank you so much for your response response in advance.
Reed

 

[Larry Linson]

Are you under the impression that all you can view in a Form (main or
embedded in a Subform Control) is a _table_? Queries are valid
RecordSource... store the ID, include both Tables, drag the ID field to the
second Table, right-click to set the Join Properties, and drag down fields,
as needed, from both Tables. It's a lot easier than it may seem from reading
this, and in the long run, not having redundant fields will save you lots of
grief.

Larry Linson
Microsoft Access MVP

 

[John Vinson]

Hello John:
Thank you for replying. I do understand your point about redunds. The
reason it is necessary is to allow the user of the form to see their
selection. The recruitment table is viewed as a subform. The user makes the
selection and needs to see both the code and the class title.

In that case - "pull" don't "push". The Class Title textbox can have a
Control Source

=comboboxname.Column(n)

where n is the zero based subscript of the class title within the
combo box's row source query. There is no reason to store the class
title in a table field (which would require "push").

John W. Vinson[MVP]

 

[Guest]

Hello Larry:
Thank you so much for your reponse. It is very much appreciated.
I will give your recommendation a try and let you know how it goes.
Again, thank you for your recommendation.
Reed

 

[Guest]

ok

Are you under the impression that all you can view in a Form (main or
embedded in a Subform Control) is a _table_? Queries are valid
RecordSource... store the ID, include both Tables, drag the ID field to
the second Table, right-click to set the Join Properties, and drag down
fields, as needed, from both Tables. It's a lot easier than it may seem
from reading this, and in the long run, not having redundant fields will
save you lots of grief.

Larry Linson
Microsoft Access MVP