1 of 1 people found this helpful
Your data model is non-normalized, to use the technical term. In plain English: you're table is wrong because you're trying to put all data about everything into one table, by using many fields.
This also makes it redundant, because each student who enrolls in a course has all the Course information. If you needed to look up or change the Course title, where would you do it?
The solution for these problems is to use more tables, rather than more fields. You give each kind of data (aka entity) its own table: One for Students, one for Courses, and a so-called join table like Enrollments, where each record is a combination of a course and a student.
The FileMaker Help System describes this structure - and how to get there - in great detail and with illustrations in the topic “Designing and creating databases -> Creating a database -> About planning a database”.