Originally Posted by
ArviLaanemets
To show users tables only adds confusion for them. To allow them to edit tables directly will be a reason for lot of problems in future. A reasonable approach is hide the object pane from users entirely, and let them interact only through forms.
You can show on forms anything you are able to read from tables, or calculate - so yes, you can display e.g. MPN with highest LC_Code in enterprise part form.
In my previous post, I advised for Status field in tblEnterpriseParts a different role - it will indicate, has the enterprise part at least one not obsolete manufacturer part listed or not. Belive me, this advice was for reason! It is easiest way to discover obsolete enterprise parts, and to filter them out in any queries you are using in your application.
From your picture I see, that you mean to register an obsolescence case, and the link it with tblManufacturerParts through CaseID. No need for CaseID in tblManufacturerParts. Instead you add an FK field MPN_ID into tblObsolescenceCases. When you have on form fEnterpriseParts a continuous subform with fManufacturerParts as source, you can have a hidden unbound control on fEnterpriseParts where MPN_ID for active manufacturer part in subform is written by Current event of fManufacturerParts. And then you can have another subform in fEnterpriseParts, linked with unbound control in parent form, where the info from tblObsolescenceCases for active manufacturer part is displayed. You can make this form disabled or invisible, when manufacturer part is not obsolete. When the part was declared obsolete and then not obsolete for several times, you can browse through all obsolescence cases for this part, add a new case, or edit existing one (when having possibility for multiple obsolescence cases for manufacturer part, it will be reasonable to order obsolescence cases in subform by Obso_iD DESC - so current obsolescence case is displayed by default).