3 Replies Latest reply on May 26, 2011 9:00 AM by philmodjunk

    database design

    mrc_1

      Title

      database design

      Post

      Hi I'm a complete newbie trying to setup a database for my wife's franchise business, She's a travel agent specializing in selling Cruises.

      At present she uses a spreadsheet to track all cruises sold commission payments ect.

      So would the following be a good start?

      Page-01.jpeg

        • 1. Re: database design
          philmodjunk

          Kp_Client_ID should uniquely identify each client. Kp_Cruise_ID would uniquely identify each cruise. They shouldn't be linked in the same relationship.

          A starting set of tables would seem to require this set up:

          Clients------<Bookings>--------Cruises

          Clients::ClientID = Bookings::ClientID
          Cruises::CruiseID = Bookings::CruiseID

          Clients would have one record for each client.

          Cruises would have one record for each cruise on which your wife can book cruises

          Bookings would log each time your wife actually books a given client on an available cruise.

          • 2. Re: database design
            mrc_1

            Thanks Phil, so would this be better?

            Not sure if I'm understanding you correctly but is this a better solution?

            Bookings

            BookingID

            Booking_REF

            Total_Fare

            Amount_Of_Discount

            Total_Gocruise_Fare

            Comm_Earnt

            Comm_Paid

            Cruises

            Kp_Cruise_ID

            Sailing_Date

            Cruise_line



            • 3. Re: database design
              philmodjunk

              You seem to have the right idea. Fields in Bookings would record the details of booking that one client on a specific cruise. Fields in the Cruises table would record sepecifics about that cruise, you might include fields for the name of the ship, the port of departure, etc. there if you need that data in your database.