Need help with Related Fields!

[Christen]

I haven't been able to find a workable solution to this,
so hopefully someone out there knows the magic answer.
I have two tables(with forms)- one for new orders (input)
and one for the completion of the order (output). On the
input form, the user enters the P/O #, Part Number, Due
Date, etc. On the output form, they enter the P.O. #,
number completed, date completed, etc. I want to set it
up so that on the input page, the user enters the part #
the description of the part automatically fills in a
separate field. On the output form, I want the user to
choose the P.O. from a dropdown list (all of the P.O.'s
entered in the input table). Upon choosing a P.O. #, I
want the part # to automatically fill into another
field. The information from the output form should be
saved to the output table and vice versa with the input
table. I have been able to get parts of this plan to
work, but not all of them and not successfully. Any
thoughts would be appreciated! Thanks!

 

[John Vinson]

I haven't been able to find a workable solution to this,
so hopefully someone out there knows the magic answer.
I have two tables(with forms)- one for new orders (input)
and one for the completion of the order (output). On the
input form, the user enters the P/O #, Part Number, Due
Date, etc. On the output form, they enter the P.O. #,
number completed, date completed, etc. I want to set it
up so that on the input page, the user enters the part #
the description of the part automatically fills in a
separate field. On the output form, I want the user to
choose the P.O. from a dropdown list (all of the P.O.'s
entered in the input table). Upon choosing a P.O. #, I
want the part # to automatically fill into another
field. The information from the output form should be
saved to the output table and vice versa with the input
table. I have been able to get parts of this plan to
work, but not all of them and not successfully. Any
thoughts would be appreciated! Thanks!

It sounds like your database has some redundant fields. Am I
misunderstanding? Surely a Purchase Order table wouldn't have a unique
relationship to a Part Number, would it? Do you generate a different
PO for every part? And why do you have an "input" table and an
"output" table... ordinarily one would store Purchase Order data in
the Purchase Order table, order details in an OrderDetails table (see
the Northwind database), part information in a Parts table; and use a
Query joining all these tables as the recordsource for a Report for
the output, rather than having an "output table" per se.

The part description can be *displayed* on a Form, but it should not
be stored in any table other than the parts table. Just include the
Description field in the rowsource of the combo box, and set up a
textbox with a Control Source like

=comboboxname.Column(n)

where (n) is the zero-based subscript of the description field in the
combo's query.

 

[Guest]

Dear Mr. Vinson:
Thank you for your suggestions!
Christen