More entity relationship questions
Along the same lines as my previous question:
I have a one to many relationship between students and rent/fees and then a one to many relationship from rent/fees to payments, as Philmodjunk suggested.
So far so good. But students can also incurr fees from periodic inspections and poorly cleaned premises at check out. so I have a one to many relationship between students and a table called Chk/Insp (For checkout and inspection). That table has a one to many relationship with rent/fees.
so in summary: rent/fees has two relationships, one from students--<chk/Insp--<Rent/fees---<payments and one from
My question is if this is redundant or superfluous? I have tow pathways to rent/fees but I feel like i need to have a table documenting check out and inspection deficiencies. is that okay?