Here is the relationhips.
I suppose the other idea .. if it's not a good idea to mix tables this way, would be to simply create a layout which incorporates the data I need.
I really need to have the info from the Homework Support Table and the work Variations table listed by date, and have them in the same area. I mean I don't realy want the work variations and the Homework support in two seperate tables. I want them listed together.
I am thinking it might be better to merge the data and filter it in the one Homework support table. I have done this on my test database and it still seems to be working ;->.
I'll think I can filter this information a lot easier now.
I think merging the tables may be a very good idea. There is also very little need to copy data from multiple fields in one table into multiple fields in another if you can instead link them in a relationship as you can then combine the fields from both tables on the same layout--there's no need for the copy except for very specific reasons such as cases where the copied data isn't supposed to change to match when the user updates the original data.
It also looks like you have way to many match fields in your relationships.