Linking records by name is a very bad idea that opens the door to quite a few problems.
Names are not unique. Names change. Names can be mis-entered. All of this creates situations where you might need to change a name and doing so then breaks the links to all your related tables unless you perfectly update the records in the related tables to match the new value in the parent table.
You can avoid these issues by linking the records by a primary key--either an auto-entered serial number or a text field with an auto-entered key produced by the get ( UUID ) function newly added in FileMaker 12.
If you have a master table--say we call it contacts. And onther table, call it orders is linked to it like this:
Contacts::PrimaryKey = Orders::ForeignKey
Then you can add name fields from contacts to a layout based on orders and the name of the related contact will appear on the orders layout when the current orders record is linked to a record in contacts by the value in the primary key field.
but who am I to question the boss?
I sympathize as that can be a tough one depending on your boss and his attitude towards you. Ideally, it should be part of your job description to question his design choices in the interest of suggesting improved alternatives--but with some individuals that isn't a practical option.
Thank you very much for your quick answer, I think I will do what you suggested with the key field. In the meantime I will get a more senior member of the staff to bring it up to him.
Once more thank you very much,