Experts:
I need some general recommendations for managing "calender-based" (dynamic data) in an Access database. Attached JPG provides a very generic query output/report. Please allow me to further elaborate on the information:
Generic Data (orange columns):
- Fields [LastName], [FirstName], [Service], [Type] are part of the "Employee" table
- Field [EmployeeID] is part of the "Billets" table
- Field [Office] is part of the "Organization" table
- In my actual DB, I have roughly 100+ fields across these tables; however, for illustration purposes, the sample data should suffice
Dynamic Data (blue columns):
- As part of the Coronavirus response, our organization tries to minimize "social interaction" (in the office) by allowing people to work from home on different days/times.
- The information in the blue fields is **totally arbitrary**.
- In this example though, we'd like to develop a matrix where we can create a report/output that will show us the "generic data" (orange fields) plus calendar-based information.
- In this case, for illustration purposes, I merely included two (2) weeks of proposed data (WHO will work WHERE & WHEN).
Here's What I Need Some Help With:
- The information in "orange" is generic and I can easily create an output query from across multiple tables.
- For those columns in blue, I'd like to get some general ideas/recommendations as to how I can create a table where **Dates are now field names**.
- In this example, I merely included a two-week range; in reality however this period of coordinating telework/office work could extent to several months.
My Questions:
- What would be the most efficient way to manage a view like shown in the attached picture?
- I am not sure if I want to manually create, e.g., 60 fields to cover a 60-day date range. So, do you have a recommendation that would allow me to store information such as "Telework" or "In Office" (by dates) without having to create a potentially infinite number of fields in new table, e.g., "Telework"?
Thank you,
Tom