>>>Just out of curiosity, how would one go about implementing the graphics compnent of this application? I have been talking to a client about a similiar challenge involving seat assignment in a large arena/venue. They would like to see a graphical representation the venue and available/unavailable seats. Any thoughts?
>>
>>This is slightly different as the seats are fixed (I hope) or if not fixed are in a few fixed configurations.
>>
>>It's quite easy, you get a diagram from them, make it into a form. Each seat has a number (usually A1 through Z999). Create a table with a record for each specific event with fields for date, event name, and any other data they need, and a field for each seat (use seat numbers as field names even) These can be logical fields if you like .T. when sold.
>>
>>They call up the event, you display it with a block for each seat which is either blank when unsold or colored when sold. If you want to get fancy you can use and integer field and use different colors for different prices and black when sold...
>>
>>It doesn't even need to be a realistic diagram just one square per seat would do...
>>
>>Jen
>
>Hi Jen, I'd make the seats into a child table. With a template table with a blank record for each seat, you could add a new event record and then append the template to the child-seat table with just a command or 2. This way you have far more options of what information is kept about each seat - reserved, ticket pickup, payment method, cost, etc.
>
>Everything else you suggested was great.
>
>Barbara

I like the child table idea because these venues can have a 10,000 - 20,000 seat capacity. I don't see how a form used for this representation would be practical. Any further thoughts?