What you want to do has very little to do with relationships and a lot to do with User Interface design--how you set up your layout(s) for data entry.
Hi, thanks for your comment. So I can set up my layout so that when I choose the material type (e.g. ceramic) it will only bring up the fields relevant to that material type?
Do you have any advice as to how I can do that?
Thanks in advance
You need to share how you've structured your tables and relationships. That forms the basis for your interface design so we'd need to see what you have to start with, to determine if it's workable and then either modify that design or work from it to suggest an interface design.
A more detailed description of your "workflow" might also be enlightening.
On of the things you said concerns me. Relationships don't isolate fields, the isolate RECORDS containing those fields. From what you are describing, the material is an element of an object you are cataloging. Please provide us with the names of the TABLES you are using, and the match field you are using to create the relationship. I do something similar in one of my files. I have a table that contains invoices, and a table that contains inventory. When a user only wants to see "shirts" from the inventory table while adding items to an invoice, I created a relationship with Categories in the inventory table and a global field, g_category in the invoice table. I use a drop down list based on all the possible categories in the inventory table. I place the list in the g_category field on an invoice. When a selection is made, the portal containing all the inventory items is filtered, and only the items matching the selection in the global field are displayed.
bek123, this can be confusing. Take a look and see if these demos answer your question. I think this is what you want: