I think your difficulty mainly lies in the fact that you don't seem to be aware that tables are not to be worked on/in directly. Table fields (not columns) are not meant to do anything based on an action taken in any other field. Lookup fields (if we're meaning the same thing) while possible, are also to be avoided.
I don't know how I can make a table or query that people can change the yes/no options and the comments.
You don't, actually. You use forms which are based on queries or tables, and the form and/or code behind the form manipulates data in the tables.
Also for the last part the notices. They will be sending many at a time, so if they are able to click yes on many at once rather than having to click yes 100+ times.
This could mean anything since you're not saying what they'd be clicking on.
You need properly designed tables, properly related to one another, then queries upon which to base the forms. If you cannot edit, add or delete info via the query, don't expect a form based on that query to behave any differently, so I personally suggest designing a query that works first. Some queries are not editable by nature; e.g. Union or Totals, or the reason could be improper/inadequate relationships. The "many" side of a one to many relationship can also present editing challenges.
So not sure what anyone can do for you at this point as not much information has been revealed. I suspect you need to research db normalization as a start....
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.