different ticket types

[fapa]

Hi

Im very new with access and i was hoping someone can help me out - im
creating a booking system that allows staff members to book yogo classes for
different types of people in one booking. All bookings are processed by staff
members of the club (customers must approach staff) and only one class can be
booked at a time. The different types of people are (students £7p/class,
adults £10p/c and OAP £6p/c) so for instance, if someone wants 3 adult
tickets and 2 student tickets for a particular yogo class, the booking system
should be able to permit this in ONE booking (therefore ONE total price and
ONE payment)

I figured out how to do this on a form (Qty*Price) however this isnt partical,
as the catch is, if i wish to add a new 'ticket type' to my booking system, i
want the booking form to automatically update this. IS this possible?

Please help!!

 

[Rick B]

One post per question please.

 

[Alec M1BNK]

Lets say you have two table of booking data, one with the customer data in,
and one with their bookings in a one to many relationship

Then, have a table with the ticket types and prices in it

In your booking form, make the customer details, then in a subform therein,
make the various entries for each of their bookings, picking the ticket types
from a combo box. Some kind of booking number would be needed to link the two.

Table 1
Customer personal details, booking details, other stuff relevant to the
booking, booking number

Table 2
Booking number, ticket type booked, quantity, unit price paid

Table 3
Ticket Type, Current Unit Price

Now, if you update the prices, or the ticket type, it will automatically
update the choices available in the subform.

BTW, this is one of the few occasions when you SHOULD duplicate one field
(ticket price) even though it already exists in another linked table. If you
don't, then seasonal adjustments in price will affect historical data too.

That's what i would do, but I am a bit new to database and Access is my
limit so far, but that would work. It might break a few rules and no doubt
someone will drop by shortly to tell you all about which ones

Alec

 

[fapa]

as staff carry out the bookings, no customer details are needed, just how
many tickets they need and of which types. i'm going to try your suggestion
now and will let you know how it goes - thanks!

Lets say you have two table of booking data, one with the customer data in,
and one with their bookings in a one to many relationship

Then, have a table with the ticket types and prices in it

In your booking form, make the customer details, then in a subform therein,
make the various entries for each of their bookings, picking the ticket types
from a combo box. Some kind of booking number would be needed to link the two.

Table 1
Customer personal details, booking details, other stuff relevant to the
booking, booking number

Table 2
Booking number, ticket type booked, quantity, unit price paid

Table 3
Ticket Type, Current Unit Price

Now, if you update the prices, or the ticket type, it will automatically
update the choices available in the subform.

BTW, this is one of the few occasions when you SHOULD duplicate one field
(ticket price) even though it already exists in another linked table. If you
don't, then seasonal adjustments in price will affect historical data too.

That's what i would do, but I am a bit new to database and Access is my
limit so far, but that would work. It might break a few rules and no doubt
someone will drop by shortly to tell you all about which ones

Alec

Hi

[quoted text clipped - 13 lines]

Please help!!