Hi,

I'm trying to do something fairly simple but not sure how to do it.

I have a list of students in my Student Master database.
I have a list of Classes in my Classes Master.
I have a list of Schedules in my Classes Master.

A many-to-many relationship exists between Students and Classes via a
join table called Enrollments.
A one-to-many relationship exists between Classes and Schedules. (Each
combination of date, time-block and room is considered one Schedule
line item. Any one Schedule line can only belong to one Class, but one
Class can be the parent of multiple Schedule lines).

I want to construct a report layout (for printing) that will show me:

1) Name of class at the top of the page, followed by each Schedule
line that belongs to it, followed by a list of Students belonging to
that class.

2) Name of Student printed at the top of the page, followed by each
Class that student will belong in, followed by the Schedule lines for
that class. Is it possible to sort this by Schedule?

3) A single report that lists out every Class, along with it's
schedule lines, along with it's Students.

I'm completely lost, because I cannot seem to overcome the hurdle posed
by going from one student to many classes to many schedules per class.

Any ideas?

In article <1166474684.738332.171600 (AT) 80g2000cwy (DOT) googlegroups.com>,
nbarman (AT) gmail (DOT) com wrote:

I think you need to treat each separate schedule entry as a separate
class assignment for the student. The relationship structure would be:

Student::kpStudentID = Enrollment::kfStudentID

Enrollment::kfScheduleID = Schedule::kpScheduleID

Schedule::kfClassID = Class::kpClassID

In other words, the students are actually assigned to Schedule records,
and each schedule record is assigned to a Class record.

--
For email, change <fake> to <earthlink>
Bill Collins

That makes sense, but then how would I assign a student to a class.
Say I need to assign Joe Brown to "Filemaker 101" which takes place on
1/1 from 10-12, 1/2 from 10-12 and 1/3 from 1-3. Would I have to
enroll Joe to each of the three sessions that the class takes place on?
Right now the way I have it set up is that I simply assign Joe to the
class, and the class is already linked to it's multiple schedules.
That way if I add or change the schedule of the class, the affect to
Joe Brown is seen automatically.


Bill ne likha tha:

My earlier response was based on the assumption that a student is
assigned to one scheduled event, or to a "section" of the class that
meets at a certain time, and further, that each schedule record is
assigned to a specific class.

On that basis, if you assign a student to a particular "schedule" that
automatically assigns him to a specific class, as each Schedule record
is assigned to a specific class.

Using the example you gave of FileMaker 101, would there be other dates
and times for the class, which Joe would not attend, but presumably
others would?

Would all the students in one group attend all the same sessions, or
might some students attend different sessions? In other words, would the
students be assigned to "sections" and all the students in each section
attend all the meetings of that course together?

If students are assigned to sections, and all members of the section
attend the class together, then each section is in effect a schedule
event, that happens to occur on different days and times in succession.

If students mix up the sessions of the class, and can not be identified
as specific sections, then I think you would need to assign each
individually to each schedule event.

There is another approach, which assigns students to classes and leaves
it to them to decide which scheduled times to attend. The description of
each class would have the dates and times listed, so the students could
pick which they want to attend. The trouble is, it would not be possible
to make a meaningful attendance sheet, and you would not know how many
students are going to come to each session.

Bill

In article <1166538704.185673.156990 (AT) t46g2000cwa (DOT) googlegroups.com>,
nbarman (AT) gmail (DOT) com wrote:

--
For email, change <fake> to <earthlink>
Bill Collins

Hi Bill,

The way I have it set up is that the classes are in sections. So, for
example, if I have a class called "FileMaker 101", I might have 5
different sections of it. For a student needing to take the FileMaker
101 class, he/she is already assigned to one of the 5 sections. Each
section has a fixed schedule. So, for example, let's say that every
section must meet on three different days for four hours. The dates
and the times have been pre-defined for each section.

Now, I just need to assign the student to all the schedules (3 in this
case) to the particular section that he/she is a part of.

So let's say John Doe is in Section 4 of FileMaker 101. Then he will
follow the predefined 3-day schedule for Section 4 of that class.

I need to be able to assign him to a class section in one step. After
that's done, I need to be able to generate the three reports I listed
below...

I'm still a little perplexed on how to do this, so any advice would be
really helpful.

Thanks!


Bill ne likha tha:

I would think it would be fairly simple to put the schedule for each
section in a text field in the record of that section. That allows a lot
of flexibility, and makes it so once a person is assigned to a section
their schedule is fixed.

In article <1166728660.320710.93770 (AT) n67g2000cwd (DOT) googlegroups.com>,
nbarman (AT) gmail (DOT) com wrote:

--
For email, change <fake> to <earthlink>
Bill Collins

That would work and I was thinking of that, but then the problem is
that I am not able to use the schedule information in the same way that
I ordinarily could - for example, I cannot sort by day, or print a
schedule by day, or run a report to see how many things are happening
at a certain time, etc...

I think there should be a straightforward way to do what I'm trying - I
just can't figure it out.


Bill wrote:

Another approach:

Schedule table: I will call it Meeting table in this discussion, primary
key field kpMeetingID, foreign key field kfSectionID, fields for date &
time, and others as needed.

Class table, primary key field kpClassID, other fields for class name,
etc.

Section table, primary key kpSectionID, foreign key field kfClassID,
other fields as appropriate.

Student table, primary key field kpStudentID, fields for name, address,
etc.

Student_Section table, a join table, primary key field kpAssignmentID,
foreign key fields kfStuentID and kf SectionID, fields for grade, etc.

Class table, primary

Relationships:

Student::kpStudentID = Student_Section::kfStudentID

Student_Section::kfSectionID = Section::kpSectionID

Section::kpSectionID = Meeting::kfSectionID

Class::kpClassID = Section::kfClassID

So, each meeting is unique to a Section, and one section can have many
meetings.

Students are assigned to Sections, many-to-many, via the Student_Section
table. Each Student_Section record is unique to one student and one
section.

Each Section is unique to a class, and one Class can have many Sections.

From this you can generate all kinds of reports and set up various
portals:

In a layout of the Student table, a portal to Assignments showing all
the Section assignments & class names

In a layout of the Class table, a portal showing all the Sections

In a layout of the Section table, a portal showing all the students, and
another showing all the meetings.

A report based on the Student_Section table showing all the students and
identifying the class

and so on with many other possibilities.


In article <1167407040.888328.217980 (AT) 79g2000cws (DOT) googlegroups.com>,
nbarman (AT) gmail (DOT) com wrote:

--
For email, change <fake> to <earthlink>
Bill Collins

Sorry about my delayed responses... I'll try out your suggestion below
soon and write back on the group if it works out.

Thanks!





Bill ne likha tha: