3 Replies Latest reply on Jan 13, 2015 1:35 PM by bvondeylen

    "Roll Over" records to the next academic year



      "Roll Over" records to the next academic year


      Hi All!

      I have a database which lists donors (active, inactive), another database which lists students (active, inactive), and yet another which lists faculty and staff (active, inactive).

      To start out with students, I'd like to find a way to "roll over" students to the next academic year, but to still have records of them from the previous year.  So, essentially, all active students, who will graduate on to the next grade will go from 14-15 academic year to 15-16 academic year on July 1 (or whenever the process is initiated). The same would go for faculty/staff, donors, etc.

      How would I best accomplish this with FM?  I'm running the latest version of FMP Adv. I don't want to lose any database information from the previous academic year.  So maybe just duplicating all active records?

      Thank you!


        • 1. Re: "Roll Over" records to the next academic year

          Do you have this in 3 databases, or 3 tables in one database?  You don't say a lot about how your database is structured.  If you could show how your tables are related, more help could be provided.

          • 2. Re: "Roll Over" records to the next academic year

            I'd use one table for students that I'd not change at all for the new school year. I'd then set up a related table (or system of tables) that contain the data for which you need to specify a new set of data for each school year.

            A script working from a found set of students--those not transferring or graduating, can generate a new set of related records in the related tables.

            • 3. Re: "Roll Over" records to the next academic year

              You will need to create several more "Tables" within your database to accomplish this, similar to any Student Information System would handle it.

              One table would contain your students. Another table would handle the enrollment data (student number, enrolled year). Another table would handle demographics (which could be split up with mutiple tables depending upon how detailed you need to be). For example, do you need to know historical data of home arrangements (student lived in house A first half of the year, then moved to house B last half of the year, then moved to house C in the next school year, etc). You could end up with over 10 tables just for student information.

              This would allow for rollover, as you would not need to modify the student table. Only ADD new records for the student enrollment for the upcoming school year.