Firstly I need every date / time combination of each film to exist in
the database as an individual entity
So for example
Austin Powers Saturday 14th 19:00 would be a different entry than Austin
Powers Saturday 14th 21:00
And if 100 seats were sold for the 19:00 show the 21:00 show wouldn't be
affected. My problem is I want to minimize the amount of data entry
required as entering each date / time / movie combination could be an
almost full time job. The ideal is to have it all on one form however
this doesn't leave much room for exceptions so I considered a form
solely for film details and starting date / ending date and another that
would take these each date and for each date ask what the show time were
- the show times would ideally stay the same as first entered and it
would be a small matter of hitting enter 10 or 12 times, or entering
extra shows or removing shows - whatever. But I really don't know how I
go about doing this. Has anyone done anything similar or have any ideas
- thanks

My second question is this - In my Access database I have for sections
like certificate a look up table with say 5 values - having used vis
data to create my main form (was this stupid) I now want to change some
of the textfields to combo-boxes, should I start again and how do I tie
a combo-box to a database - I'm sure this is really easy

My third question is, in my booking section I have an on screen array of
buttons 0-9 as a control array with Index as Integer, I have the value
the user hits coming up in a text field, and the value being something
like

Dim inNoOfTickets As Integer

Private Sub Cmd_Click(Index As Integer)
TxtNumberSelected.Text = Index
Index = inNoOfTickets
End Sub

However this means you only get the last number you clicked so if you
want 12 tickets you get 1 and then 2
How do I get it to accept 12 or any 2/3 digit number  - again an easy
one I hope why are the easy ones always so annoying :) thanks again

Andrew

I'm responding only to your 1st issue.

Have a look at my web site (link below) for the "Charter Management"
application.  It's essentially the same sort of a reservations system.  You
have an asset (theater/screen), an event (a showing of a film, that has a
start time, a duration, and details like title, director ect), and you have
customers taking seats for the event.

If you make the event record the central item in the db, then the set of
events for a day shows the utilization of the theaters for that day.  And
the movie data is entered only once.  A movie is assoc. to one or more of
the events when the event is scheduled.  Customer tickets are created in
relation to a specific event.

One of the things that gets tricky is dealing with canceling an event after
some number of tickets are sold.  Perhaps it doesn't happen often for
theaters, but boats break down and bad weather forces cancellations.  The
process of canceling and re-scheduling customers is complex.  You will need
to decide if such a process is needed in your app.

Let me know if I can be of further help.
--
Regards
/Don Ames
GUU Software Inc.

Please visit our web site at...
http://www.access.digex.net/~guu_sftw