Looking at just your last database here are the issues with your tables I see:
1. Invalid foreign key. A foriegn key is the data you store in one table to relate it to another. You've related AttendT to MainT via [Member] to [Full Name]. That is incorrect. You have an autonumber primary key in MainT--that's its express purpose, to be used as a foreign key. Use its value in AttendT, not the [Full Name] field.
2. Poorly named fields. [Count] is a reserved word (
https://support.microsoft.com/en-us...n-access-2002-and-in-later-versions-of-access) which means it has special uses within Access. Do not name anything with a reserved words or it will cause issues with query and code later on. Also, avoid non-alpha numeric characters in field names ([Full Name]-->[FullName], [Phone #]-->[PhoneNumber]).
3. No date fields. A person can attend the food pantry more than once, right? Your database doesn't accomodate that.
4. No notes. In design view of your tables there's a field to add a description to what that field is for--use it. For example, that aforementioned [Count] field--its not intuitive to me what it is holding. Descriptions would help me (and people in the future who may work on your database) know what it is for.
5. Discrete data stored together. Every distinct piece of data (Address, Post Code, zip) needs to be stored in its own field. Those 3 pieces of data should each be in 3 fields, not 1. Same for [Full Name] data.
You have a lot of work on your tables before you even need to think about your forms.
In fact, after you have fixed your tables, you focus on building reports to get data out of your database. Once that is done, then you can work on forms. So put those out of your mind for now.