One-to-many

[TEN]

Hi fellow Access developers

Here is my problem.
I created a database for an organization I volunteer for but I’m running into design problems. I want the database to be able to assign preferred days of the week (that the volunteers want to serve) with the flexibility to change them.

The problem is in order to be able to keep my reporting options flexible. I will have to write a record (on a separate table) for each volunteer for every day they want to serve. A one to many relationship between the volunteer table and preferred days table.

I have not touched Access in over 6 years and I’m very rusty. Before I retired I was fluent in VBA (I used to be good at structuring too, but oh well), query criteria etc.. So whatever you suggest I can accomplish, although it might take me a minute to remember how.

I hope that made sense.
Thanx,
TEN

[June7]

I don't understand the issue. Why is the related table a problem? That is proper normalized structure.

Might find this of interest https://www.accessforums.net/databas...ses-18459.html