Can anyone help with this access exercise?

[ssanfu]

OK, you got this far.This is how I would design the tables.

[CarlettoFed]

As previously reported, the correct management of the various properties of the fields and indexes in the tables is missing, see for example:

tblStudentMember

properties of fields FirstName, Surname and RegistrationDate should have the Required property set to True which would not allow you to create records without data that are considered indispensable.

table indexes

the index ID should be deleted as it duplicates PrimaryKey with unnecessary use of space in the database
creation of at least one unique index (example FirstName, Surname) that does not allow the creation of duplicate records (as occurred in the example posted by ssanfu (records 1 and 2 rob missing, records 3, 4 and 5 steve missing, record 6 , 7 and 8 sam missing)

[harrywillson21]

when i put foreign key in enrollemt table I can't have one to many relationship. How should I do it then?

[kd2017]

If you inspect ssanfu's diagram you can see they had no issue creating the one-to-many relationship. Not knowing exactly what your doing there could be a couple things causing your issue.

First, in the enrollment table make sure that the individual foreign key fields have indexes but DO ALLOW duplicates. (You do need a unique multicolumn index too but this is an entirely different index. Here's another tutorial on multicolumn indexes https://www.geeksengine.com/article/composite-unique-index-access.html )

Second, in the relationship window drag from the primary key field from your student or trip table and to the corresponding foreign keys field in the enrollment table.