Seems like you'd want to have one Person table and one Roles table. Give each record in each table a primary key and connect the two with a join table. In this way one person could have one or more roles. Create a portal on a Person table layout to see the various roles a person holds/held.
When dealing with like items (in this case people), it's best to keep their basic information all in one table.
Just my 2 cents,
Ok that sounds like a good idea but still need a little help. When you say give each record in each table a primary key what do you exactly mean? A number or something?
Sorry but I just need to get my head around how I am going to do it.
You'll create an auto entered serial number field in your Person table. This will be your primary key for this table. Call it pk_Person. Also create any other fields specific to a person.
You'll create an auto entered serial number field in your Roles table. This will be your primary key for this table. Call it pk_Roles. Also create any other fields specific to a role. The role field (in the Role table) will be a value list containing Student, Staff, Client, Child etc.
You'll create a third table called a "join" table. The join table will contain 2 fields - call one fk_Person and the other fk_Roles. (Foreign keys relating to the Person and Roles tables)
Go to File /Manage /Database and create a relationship from pk_Person to fk_Person and from pk_Roles to fk_Roles.
Create a layout containing the fields you want.
I tried to create a prototype of this and unfortunately needed to create the same person over and over again for each new role.
Perhaps when you get a little further along you can repost your question to this forum.