Hi,

I'm thinking about a reservation system for various water sports and transportation to a nearby island. I've done a similar system in the past (boat reservations for various tours), and used the following type of organization:

GroupReservation Table: date, time, tour, tour agency, etc.

PaxReservation Table: name, pax type (child, adult, infant, etc.), tour options, price, etc.

Pretty straightforward. The implementation for maintaining pax info displays a grid of pax info, the user can select one or more and change pax type and tour options. In this case, the name of the pax was required.


This new system is a bit different. No need to have individual passenger name, just a count of pax type and tour options AND, independantly, a count of types of return transportation (both boat and land). These counts do not necessarily refer to the same group of pax.

I'm having trouble wrapping my mind around how to do this, and am considering something like:

GroupReservation Table: date, time, tour, tour agency, etc.

PaxOption Table: pax type (child, adult, infant, etc.), tour options, count, price, etc.

PaxWaterReturn Table: water return mode, count

PaxLandReturn Table: land return mode, count

Any comments/input?

I don't want to have the user necessarily enter the return modes for each individal pax...often they will all be the same. I think I'm getting stuck on picturing how the user would enter these "passenger collections" (options, water return and land return)....any input is appreciated. Guess I'm picturing a grid, and users can add and delete entries in the different types of collections.

TIA

J