In the meantime I also did some research based on your suggestions and my early conceptual design. I can say that your comments were very helpful and it has solved many of my conflicts!
thanks.
Main Topics
Browse All TopicsI am setting up the conceptual schema (i.e ERD) for a flight reservation database but have found some difficulty when it comes to relating flight schedule tables and seat allocation. What I need is a sample mdb database to get some ideas from the 'relation schema' or a URL which would possibly offer such sample databases or reference.
I thank you all in anticipation!
regards,
katmas
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: DukeyTooPosted on 2002-10-10 at 21:03:13ID: 7325475
Having never worked on a flight reservation db, I probably do not understand the complexities involved, but this would be my suggestion:
* PlaneType - types of planes, e.g. Boeing 747.
* SeatLayout - a type of seat layout (not really necessary unless many plane types share the same layout)
* SeatLayoutDetail - the seat numbers, and other info for a particular seat layout (such as "is it near the emergency exit", or "is it a preferred seat for frequent flyers".
* Plane - an actual plane
* PlaneSchedule - the schedule for a particular plane, (consists of a single flight only from takeoff to landing)
* Passenger - passenger details
* PassengerTicket - passenger ticket details, including seat allocation
* PassengerBooking - ticket booking, groups tickets together, e.g. for people travelling together
A PlaneType has a SeatLayout which has some detail of SeatLayoutDetail.
A Plane has PlaneSchedules.
A Passenger has a PassengerTicket for a PlaneSchedule.
A PassengerTicket links to a SeatLayoutDetail record.
A PassengerTicket is part of a PassengerBooking.
Whew. Sorry, no sample db, I need to catch up on my sleep :)
In retrospect, perhaps PlaneSchedule should have been called PlaneFlight.