B
Bruce
I have a database for keeping track of employee training.
It contains an employee table (tblRoster), a training
session table (tblSession), and a table (tblEnrollment)
for recording the attendance at a particular training
session. tblEnrollment is a junction table, containing
the PKs [EmployeeID] and [SessionID] from tblRoster and
tblSession (these are FKs in tblEnrollment), and the date.
Form names are related directly to the table names, so I
have frmSession and fsubEnrollment (a subform within the
detail section of frmSession). I enter the session
information (subject, instructor, etc.) in frmSession,
then enter the attendees in the subform.
When a training session is planned, a sign-in sheet
(report) is printed. It consists of rptSession and
subreport rsubEnrollment, and works fine unless there are
more attendees than can fit onto one page. When that
happens the subreport runs through the main report's page
footer, and truncates there. When the subreport reaches
the footer, I would like it to continue onto a second page
with the session information at the top of the page, just
like the first page.
rptSession contains a varying number of fields, and
rsubEnrollment contains a varying number of records. Can
Shrink and Can Grow are set to Yes in the some of the text
boxes in the detail section, the detail section itself of
the report. Subreport detail section is just tall enough
for one record (Name and date). It can grow.
I am not using grouping. A page break after the subreport
(in the main report's detail section) separates the
training sessions, including attendance, by page.
I think I have provided the relevant information, but can
provide more details if needed. I should say that there
are sound reasons for proceeding as I have in terms of
structure. This database accomplishes much more than
generating a sign-in sheet, and it generally functions as
planned.
It contains an employee table (tblRoster), a training
session table (tblSession), and a table (tblEnrollment)
for recording the attendance at a particular training
session. tblEnrollment is a junction table, containing
the PKs [EmployeeID] and [SessionID] from tblRoster and
tblSession (these are FKs in tblEnrollment), and the date.
Form names are related directly to the table names, so I
have frmSession and fsubEnrollment (a subform within the
detail section of frmSession). I enter the session
information (subject, instructor, etc.) in frmSession,
then enter the attendees in the subform.
When a training session is planned, a sign-in sheet
(report) is printed. It consists of rptSession and
subreport rsubEnrollment, and works fine unless there are
more attendees than can fit onto one page. When that
happens the subreport runs through the main report's page
footer, and truncates there. When the subreport reaches
the footer, I would like it to continue onto a second page
with the session information at the top of the page, just
like the first page.
rptSession contains a varying number of fields, and
rsubEnrollment contains a varying number of records. Can
Shrink and Can Grow are set to Yes in the some of the text
boxes in the detail section, the detail section itself of
the report. Subreport detail section is just tall enough
for one record (Name and date). It can grow.
I am not using grouping. A page break after the subreport
(in the main report's detail section) separates the
training sessions, including attendance, by page.
I think I have provided the relevant information, but can
provide more details if needed. I should say that there
are sound reasons for proceeding as I have in terms of
structure. This database accomplishes much more than
generating a sign-in sheet, and it generally functions as
planned.