I want a portal, I need a portal <-- quoting you.
This means that you are already sure about your data structure and the way transactions should behave.
You don't explain what the data flow is and what it should be - you force readers to stress themselves to escape from the cage you've built around yourself.
Bad approach, IMHO.
Explain what you want, not what it should be.
"No matter what the relationship joins are between Daybook2 and Booking2 Daybook is NOT related when I go to choose fields."
That would be the expected result. Linking the Daybook2 table occurrence to another table occurrence in a relationship does NOT link daybook in a relationship.
OK I'll try and put the question another way. BTW I used this data structure because that's how I do it with Numbers (Excel to the Windows people).
I have these two sets of tables. I would like to use two fields from the Daybook (bank_date and amount_credit) for the client's payment and show them in a portal on a layout based on the Booking table as the attached image shows.
The common field is date_arrive, which is unique. (One client may be repeat bookings. only one client can arrive on a certain day. )
Can you tell me what the relationship between Daybook and Booking, be?
I got it all to work.
I hope no-one found this stressful.