I have a set with two tables as follows:
Parent Table:
*New_Name c 33
*Prod_Code c 9
Property_Number c 9
Property_Sub c 9
Child Table:
*New_Name c 33
Pun c 9
Suffix c 9
*Prod_Code c 9
then 5 others fields of various types, character, numeric, and logical.
The Parent and child are linked together in a One to Many relationship by an expression that ties the New_Name and Prod_Code fields together as denoted by the *.
First of all, if you try and link a set in this way using the referential integrity button other than "None", it gives you this message after you press ok "for integrity, use parent field name". If you agree to only link on one field without an expression, it allows you to cascade adds and deletes for example. I am not sure I understand first of all the reasoning for this limitation but that is a separate question from the real question in this topic.
So, back to the table in question, which works as described in the paragraphs above:
If I use a setup form which I call "Property Setup Screen", I have the four parent fields on the top, and an embedded browse layout for the bottom part of the form. Within the browse layout, the linked fields appear of course. But it seems redundant to have to fill in the "New_Name" field and the "Prod_Code" field in the embedded layout. If I am entering a new record at the set level rather than at the table level, then I want to be able to have some means of automatically feeling in the New_Name and Prod_code fields in the child based on the entries I have just made to the new record of the parent table.
So, how can I eliminate the need to keep the fields in both parts of the form?
Thanks
Bruce
Parent Table:
*New_Name c 33
*Prod_Code c 9
Property_Number c 9
Property_Sub c 9
Child Table:
*New_Name c 33
Pun c 9
Suffix c 9
*Prod_Code c 9
then 5 others fields of various types, character, numeric, and logical.
The Parent and child are linked together in a One to Many relationship by an expression that ties the New_Name and Prod_Code fields together as denoted by the *.
First of all, if you try and link a set in this way using the referential integrity button other than "None", it gives you this message after you press ok "for integrity, use parent field name". If you agree to only link on one field without an expression, it allows you to cascade adds and deletes for example. I am not sure I understand first of all the reasoning for this limitation but that is a separate question from the real question in this topic.
So, back to the table in question, which works as described in the paragraphs above:
If I use a setup form which I call "Property Setup Screen", I have the four parent fields on the top, and an embedded browse layout for the bottom part of the form. Within the browse layout, the linked fields appear of course. But it seems redundant to have to fill in the "New_Name" field and the "Prod_Code" field in the embedded layout. If I am entering a new record at the set level rather than at the table level, then I want to be able to have some means of automatically feeling in the New_Name and Prod_code fields in the child based on the entries I have just made to the new record of the parent table.
So, how can I eliminate the need to keep the fields in both parts of the form?
Thanks
Bruce
Comment