Instructors who are also students

[RealKangaroo]

I am using a template to track Adult Education at a church. The template has
two tables (students & instructors). However, in my situation, a person is
sometimes a student and sometimes an instructor. I don't want Person A to be
a separate record in each of these two tables, so I am thinking of a table
called tblPersons into which ALL people/addresses/etc would go. Then, in a
form called Classes, there would be a field called instructor. I would pick
from the tblPersons the name of the instructor.

Any suggestions or comments?

 

[Ken Snell [MVP]]

That is a good approach, but instead of storing the name of the instructor,
store the primary key of the person from the tblPersons table.

 

[Graham Mandeno]

You might also like to add a yes/no field to tblPersons named
"IsInstructor". That way, when you are selecting the instructor for a
class, say from a combo box, you can narrow down the choices so you don't
need to wade through a list of all the records in tblPersons.

 

[John... Visio MVP]

Good point, but I would suggest going one step further with a seperate table
that links person with courses they can teach.

John... Visio MVP

You might also like to add a yes/no field to tblPersons named
"IsInstructor". That way, when you are selecting the instructor for a
class, say from a combo box, you can narrow down the choices so you don't
need to wade through a list of all the records in tblPersons.

--
Good Luck

Graham Mandeno [Access MVP]
Auckland, New Zealand

I am using a template to track Adult Education at a church. The template
has
two tables (students & instructors). However, in my situation, a person
is
sometimes a student and sometimes an instructor. I don't want Person A to
be
a separate record in each of these two tables, so I am thinking of a
table
called tblPersons into which ALL people/addresses/etc would go. Then, in
a
form called Classes, there would be a field called instructor. I would
pick
from the tblPersons the name of the instructor.

Any suggestions or comments?

 

[Graham Mandeno]

Hi John

Yes, certainly! I'll see your "good point" and raise you one

--
Cheers,
Graham

Good point, but I would suggest going one step further with a seperate
table that links person with courses they can teach.

John... Visio MVP

You might also like to add a yes/no field to tblPersons named
"IsInstructor". That way, when you are selecting the instructor for a
class, say from a combo box, you can narrow down the choices so you don't
need to wade through a list of all the records in tblPersons.

--
Good Luck

Graham Mandeno [Access MVP]
Auckland, New Zealand

I am using a template to track Adult Education at a church. The template
has
two tables (students & instructors). However, in my situation, a person
is
sometimes a student and sometimes an instructor. I don't want Person A
to be
a separate record in each of these two tables, so I am thinking of a
table
called tblPersons into which ALL people/addresses/etc would go. Then, in
a
form called Classes, there would be a field called instructor. I would
pick
from the tblPersons the name of the instructor.

Any suggestions or comments?

 

[John... Visio MVP]

Thank You.

John... Visio MVP

Hi John

Yes, certainly! I'll see your "good point" and raise you one

--
Cheers,
Graham

Good point, but I would suggest going one step further with a seperate
table that links person with courses they can teach.

John... Visio MVP

You might also like to add a yes/no field to tblPersons named
"IsInstructor". That way, when you are selecting the instructor for a
class, say from a combo box, you can narrow down the choices so you
don't need to wade through a list of all the records in tblPersons.

--
Good Luck

Graham Mandeno [Access MVP]
Auckland, New Zealand

I am using a template to track Adult Education at a church. The template
has
two tables (students & instructors). However, in my situation, a person
is
sometimes a student and sometimes an instructor. I don't want Person A
to be
a separate record in each of these two tables, so I am thinking of a
table
called tblPersons into which ALL people/addresses/etc would go. Then,
in a
form called Classes, there would be a field called instructor. I would
pick
from the tblPersons the name of the instructor.

Any suggestions or comments?