Best Practice - Related field vs Actual field
Looking for some input/recommendations/suggestions on what would be considered "best practice" for the following scenario. I have a Clients table and it is related to the Contacts table as follows:...
Forum Discussion
We typically leave the related field alone and remove it from all reports, forms etc. The Related comes in handy when you want to start changing its value and see the text in the [Contact Name] field change. The benefits of this are that you can style the Name field. Or you can make it read only. Or other features that do not affect the related field.
If the related field gets corralled, the relationship suffers. So best practice is to leave the related field alone and remove it from User view.
Also uncheck the add everything to the form and add everything to the report. Then when you add a field for testing or something, your Users don't start asking why there is a field named test on their Default Report or on the main form.
------------------------------
Jim Harrison
------------------------------
If the related field gets corralled, the relationship suffers. So best practice is to leave the related field alone and remove it from User view.
Also uncheck the add everything to the form and add everything to the report. Then when you add a field for testing or something, your Users don't start asking why there is a field named test on their Default Report or on the main form.
------------------------------
Jim Harrison
------------------------------