Data entry layout for Parent/Child tables - ideas?
I am making a database for our holiday apartment rental, have a look at the entity/relationship diagram below.
Houses are fairly static, and I implement that via a dropdown in the Booking Layout.
Where I have doubts is how best to do the data entry layout for Guests and Bookings. The relationship is one to many (we do have guests coming back), but when entering and editing data I am only interested in seeing one booking along with the guest data (from Contact Table). Ideally I should be able to search and choose guest name (if repeat) or enter a new, along with booking dates etc.
I am comfortable with basic DB theory (have used DB2 on mainframe), but very new to frontends.