Just a start. At a minimum these tables:
Customers
========
CustID
LName
FName
Add1
Add2
etc.
Clients
=====
ClientID
OrgName
ContactLName
ContactFName
etc.
Bookings
=======
BookID
CustID - from Customers
ClientID - from Clients
ClientRateID
BookDate
ReBooked - boolean YN
etc.
Insert a new record when re-booking and check the Rebooked field.
Billings
======
BillID
BookID
AmtDue
DateDue
DatePaid
etc.
Northwind, the mdb that came with Access had a lot of good tips and info into what you are trying to do.
Main Topics
Browse All Topics





by: stevbePosted on 2007-07-12 at 12:28:13ID: 19475239
One thing to consider from a business perspective ... you might want to track not only that the date changes but also track why it changed ... bad weather, deposit bounced, equipment failure, changed their minds, had a parachute accident, date was keyed incorrectly, etc.
tblParty - this is your flight master ... you only need to track *who* paid for it.
PartyID
PartyDepartureDate
PartyBookedDate
PartyFlightDate
CustomerID
As for date changes ... you could add a field for *reason* and maybe to keep from having to do MAX(FlightDate) sub-selects for all your queries add a status field to track which are the *real* records to be used as a simple filter.
tblCustomer - ... all booking customers and all participants
CustomerID
CustomerName