June 8, 200916 yr Newbies I'm trying to create book lists for high school students. Ultimately the data will be pulled live (read-only) via ODBC from the student information system the school uses, but while I develop the book lists I'm just replicating the tables in Filemaker (so I don't need an Internet connection to do my work). So the tables were defined by the student information system, not me. I have the following 3 tables: Students (one record per student) -student ID number -last name -first name -grade Schedules (one record for each class the student is taking) -student ID number (matches the one in Students table) -course number -period -teacher Courses -course number (matches the one in Schedules table) -course title -textbook1 -price1 (price for textbook1) -textbook2 -price2 -textbook3 -price3 I'm trying to produce one printed sheet per student. It lists the student name at the top, then each course, and under each course the book(s) and price for that course. I have tried layouts based on all 3 tables, and tried putting data in the header and multiple sub-summaries, but cannot seem to get the output I need. It seems like it would be easy, but for some reason I can't get it quite right. Any suggestions?
June 8, 200916 yr Your subsummary report should be based off the schedules table, grouped by studentID. You can put the related course info in the body part and the student information in the subsummary part. Also, you may want to consider putting textbook1,2,3 and corresponding price in either its own table or at least records. Dont forget to sort by the break field which in this example would be studentID.
June 9, 200916 yr Author Newbies Thanks, after messing around with those suggestions I think I'm finally on the right track. Just have to clean up the appearance. Once that's cleaned up, I should have one sheet per student. Right now it's anywhere from 2-4. Just got confused by the different part definitions and how each one is supposed to be used. I guess I need to study up on those. Thanks again.
Create an account or sign in to comment