I'm not angry. I am disappointed that you think you've got the answer though. Good luck.
I remember my journey learning Access which continues to this day. You'll eventually figure out that the people who answer your questions are answering from the pain of having made the same mistake themselves. But, when you remember your solution to the mistake, you are then able to help someone else. In my case, I've been using RDBMS' since long before I discovered Access so I never did attempt to create a solution by creating fields on the fly. I always knew that would be wrong. I came to Access already understanding relational database design. But there is still always the siren call of ignoring normalization and resorting to hard coded buttons, checkboxes, etc and we see it frequently enough to relate.
Nothing you have said so far has convinced me that you have the solution you were originally looking for. The database arnel posted is a start but it is incomplete. It gives you an idea of how the data should be stored correctly but that is only part of the problem. I tried to explain how to get all the way but you don't seem to have any interest or you simply cannot yet see that your solution is incomplete so let's just leave it at that. If you ever decide you want to see the example I intended to post, let me know. Eventually, you'll get tired of having to enter each row separately.
I'll obviously have to get much more confident with the design and use of sub-forms.