Excellent. So to further clarify the issue you are contending with, lets say for example that you have a field in Aspen Students called Emergency Phone Number and you have created a lookup field in the Student Athletes table to pass the Emergency Phone Number field to child records in the Student Athlete table. Finally lets assume that you have add the Aspen Students - Emergency Phone Number field to a form or report visible to your end users.
Is the issue that your end users can see the Emergency Phone Number field when viewing the Aspen Students record, but cannot see it when viewing a related child record in the Student Athletes table?
If the above is true, then lets determine whether as the application administrator you can see the fields in both records or if it is also "hidden" . If the administrator role can see the field, then we have confirmed that it is in fact a permissions issue for the end users rather than a database relationship or form design issue that is preventing your end users from seeing the information.
