Thank you for your clarification of using unique ID, I current have registration ID which it is unique to each registrations.
Hmmm, but eventually I will add more tables, to organise invoices, assigning the job to specific person, etc... I am not sure if one table would be sufficient?
Perhaps I should explain more clearly, we run community classes, the people who would like to attend the course, they register online. I can export the registration into csv or excel, then import into FM.
Some people may register more than 1 course, and in that case, the email list would be duplicated. SO that's the reason I am trying to make another related table, using email as unique id to ensure it is not duplicated, and will update the course list's email if the person's email changes, so i can send the certificate via pdf directly to specific class, etc.