Possible approaches:
- find out why Excel macros are not stable and fix that. Excel is the better tool for your layout
- considering the mantra "Normalize until it hurts, denormalize until it works" take the denormalize part to heart. Create a project table with fields for each day, but trying to have 2 Saturdays and 2 Sundays would be a deal breaker. However, you will find that extracting data based on days will always be a problem and if you post issues about that here, you will probably get told your schema is all wrong every time.
- key thing to remember is that with Access, storage is one thing, presentation is another. I'm not saying this is a great approach, but I would think you could store the data properly and use a continuous form to pivot and present it. I'm thinking that the presentation would involve a crosstab query to pivot the weekday row data into day columns. However, this assumes that you would be able to group by Day values so that you restrict column results to the 7 days. Again, 2 Sat/Sun is a no-go.
That is all speculation because as noted, Access is not meant to be used as a spreadsheet and it's likely that not many helpers here would be very interested in such a project. Perhaps an Excel forum could help you with the macro corruption issue.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.