Trying to generate a report with two unrelated repeating sections

[Toxeia]

I'm working on a school service learning project in which we are creating a simple database for an organization that provides support to family's that have children with diabetes. They are interested in demographics in terms of where these kids are which is simple enough to handle with a query. However, there is a form we are trying to create almost as a proof that everything is working kosher-like. It's to mimic the form used to collect data from the families while they are in the hospital. It includes basic information about the patient/child, information about their guardians/parents, and asks if they have any siblings, as well as their age.

Here is a example I threw together in word just now to depict what I'm looking to do: https://i.sli.mg/GNLhPY.jpg

The jist of it is the report would be broken up by the patient, then inside the patient I'm looking to have the guardians and siblings repeat independently inside of the patient. Probably the easiest way to show what I'm thinking is this.

What I'm getting: https://i.sli.mg/wE01lB.jpg
What I really want: https://i.sli.mg/532Gpj.jpg

You'll notice that in the second one, Guardian and Sibling are level with each other. That's just MS Paint though.

Finally, these are the relationships I'm working with right now. Maybe one of you will look at it, decide I'm an idiot, and explain a better way to do it. I'd greatly appreciate it.
Relationships: https://i.sli.mg/6nNY5P.jpg

PS: Sorry, as a new user I can't make those into hyperlinks.

 

[Ranman256]

the parent Patient table will have 2 sub tables,
tGuardians and tSibs

tSibs will have a field GuardID

 

[Toxeia]

Is that the phenomena where the entries on the table expand to show their relations? I wasn't seeing that after building those relationships.

I did find a way to get what I wanted, and I meant to post it on here before getting to bed, but it was already 3 in the morning. What I did was break the multi-value GuardianIDs into two fields, GuardianID1 and GuardianID2. Then I created two sub-reports that referred to the GurdianInfo table against GuardianID1 on one sub-report, and GuardianID2 on the other sub-report. This only lets me define two guardians, but that's alright. Then the section with siblings can repeat without interfering with others.

 

[Minty]

This is one of the problems with Multivalued fields, and why most developers shy away from them. They aren't always supported in other database formats if you ever upscale. More here: http://stackoverflow.com/questions/1461582/multivalued-fields-a-good-idea

 

[Toxeia]

Oh, alright. Thanks Minty, that link made me understand what it was Ranman256 was saying. I don't know why that didn't occur to me while we were planning out the database. We probably just saw that multi-value was a thing and thought it would solve that problem for us.

Oh well, we have our solution, even if it isn't perfect. Given this is for a school grade it's not that big a deal. If the client decides to implement what we've produced we can correct it then.