This doesn't sound like a good approach overall. You should be using relationships to refer to records in other tables, not calculations. I am afraid I cannot say more than that without understanding what your solution is supposed to do.
I'm trying to make a school schedule.
Different kids (CONTACTS) are enrolled in different classes (REGISTRATION) which are then displayed on their schedule (SCHEDULE) which is broken down by periods and days. While all the data about their classes is written in the REGISTRATION table, I need that data to post accordingly. From everything I've tried, making another table where the data gets copied over seems to be the right way (as this would be a sort of hybrid style from a previous database we had)
I am afraid that's still very sketchy. Do they register for classes (if so, where is the Classes table?) or does each student have their own private scheduling (as is in music lessons, for example)?
In the first case, the schedule would be a child of Classes, and each student's schedule would be given automatically by enrolling into one or more classes. In the latter, Schedule would be a child of Registrations, not of Students.