Display the description on the form

[Guest]

If I have several tables: Table1 contains 1) Industry_class_code and 2)
industry_class_description, Table2 contains 1) customer_no and
2)customer_description. Table3 contains 1) division_no and 2)
division_description. Table4 contains 1) parent_number and 2)
parent_description. On my form when you select the Customer_description
(i.e. GM), the related Parent_description (GM) is linked/pulled and
displayed. The Divisions could be Buick, etc. However, I can't seem to get
the Industry_class_description (OEM) to display. The relationship between
Parent_no and Industry_class_code 1 to 1 since all parent_description="GM"
are "OEM". What is the best way to get the description to display? Should
it be an unbound field?

Thank you,
gg

 

[John Vinson]

If I have several tables: Table1 contains 1) Industry_class_code and 2)
industry_class_description, Table2 contains 1) customer_no and
2)customer_description. Table3 contains 1) division_no and 2)
division_description. Table4 contains 1) parent_number and 2)
parent_description. On my form when you select the Customer_description
(i.e. GM), the related Parent_description (GM) is linked/pulled and
displayed. The Divisions could be Buick, etc. However, I can't seem to get
the Industry_class_description (OEM) to display. The relationship between
Parent_no and Industry_class_code 1 to 1 since all parent_description="GM"
are "OEM". What is the best way to get the description to display? Should
it be an unbound field?

Thank you,
gg

The simplest way is to simply use a Combo Box with both the Parent_no
and the description displayed. You can set the ColumnWidth property of
the combo so that the Parent_No is the bound column but is of zero
width; that way the computer sees the (unique but meaningless) number,
and the user sees the description, and both are satisfied.

HOWEVER... I don't think you have a real "one to one" relationship
here, and if you do, maybe you can simplify your table structure! A
one to one relationship means that every record in the Parent table
has either zero or one matching records in the Child table, and all of
these child records are different. That is, it would imply that Buick
has one industry_class_code, Chevrolet a different one, Hupmobile a
third. It sounds to me like you have instead a one
(Industry_Class_Code) to Many (Division) relationship; each Division
has one and only one industry class code, but one industry class code
(OEM) may have many industries. Is this correct?

John W. Vinson[MVP]

 

[Guest]

Hi John,

Do I also need to input the Parent_no into the Industry_class table so that
both have the same keys, and then link on that same field? Or, do I add in
the industry_class into the Parent table? Yes, you are correct. One
industry_class can have many parent_no. How do you know which table to add
the corresponding key field to?

Thank you for your help!

gg