Help with a seat booking system esspecially Pat Hartman!

i was looking at a post posted a while ago asking for help on a seat booking system and Pat Hartman posted a great reply which sounds like exactly what i need but there are some things i dont quite understand

im quite new to access but i think i understand the basic concepts


the link to the post is :
http://www.access-programmers.co.uk/forums/showthread.php?threadid=4696


Basically i dont know how to create the FloorPlan Table and Event seats tbl


in the tblFloorplan;
is it proposing creating a seperate record for each row defining which row it is and which section it is on and then defining which seats are on the row?

and for the tbleventseats

i dont quite understand how this table will be created from the floorplan tbl and i also dont understand what is meant by "seat1bookedflg" or "bookedtoID"


i hope non of these questions sound stupid but as i said i am new to access

if anyone understands this and could help explain or possibly create a small access file showing me what the 2 tables look like that would be great or better still a simple version of all of it running together!!


thanks alot


Matt

Matt, the outline I posted was just a suggestion. Without doing the requirements gathering and some analysis and design, I would not be able to tell you exactly how to create your tables. The idea of using a floor plan table is simply to give each show a template of how the seats are arranged. As I said, even in a theater with fixed seats, there are reasons that seats become unsalable. So, basically, the template table defines the fixed seats. You copy it for a specific production and black out the seats that cannot be used due to the staging of a particular production.

This is one of those applications where the presentation of the data would be easiest if the table were not normalized. So, you need to decide if the ability to use bound forms overrides the need to store the data in a normalized table for analysis purposes.

In the Floorplan table, the seat fields store the seat id that will be printed on the tickets. In the EventSeats table, the seat fields store the id of the customer who booked the seat.

supernintendo, I don't really have time to build a working sample for you. Without knowing your specific requirements it would simply be a waste of my time.

hey , thanks for your help anyway i think i have worked out how to do ita slightly different way anyway


thanks again
Matt