" However, is it possible for you to give a real world example.... "
-- Lets say you are trying to identify employees and all you know about these employees is their DepartmentName, FirstName, LastName, and JobCode for what part of the department (this is obviously highly unlikely but i'm trying to create a small example). If you are to place these employees into an Employee table, you need 1 thing that seperates each one from the other "uniqueness". Since this example lacks the luxury of social security numbers or employee ID's .. it creates a dilemma. But through inspection you find that, DepartmentName / FirstName / and LastName together as a group is unique for each employee.
"Also how do you plan to group the fields, by using multi column dropdowns?"
-- I believe i would have to. It will take at least 3 fields (in the above example) to seperate each employee from the other. So, in order to relate the Employee table to another table such as an "Employee Info Table" or "Employee Jobs Table" , we would need to use all 3 fields together. I'm not sure if you're familiar with database design but this would be referred to as a "Multi-Fielded Primary Key" i believe in most database software. Specifically how I get teh fields grouped depends on the software, method uses dropdowns for relationships so I assume this is the only possibility, if the possibility exists.
"..have you decided which would be your child and parent tables"
-- I regret to say i'm not sure what you mean by the parent and child tables. I understand the relationship between two tables but have never seen them given such identifiers as "parent".
"...and how to link them?..."
-- If by 'link' you mean 'relate' then that should be made more clear above. If not, you will have to fill me in on what else 'link' could refer to.
_____________________________________________________
Thank you for your time on this,
~Joe