T
Tim_S
Hey, I'm preparing for a final and doing some practice databases(this is only
a fundamentals course so please excuse if the answer is rather obvious).
Here's the scenario that I'm working on. Sorry for how long this is, and
hopefully this is the right section to put it.
Sally Sniggins runs a small concert hall that promotes local Jazz bands.
Currently, she handles all
the ticket sales by hand, and doesn’t track where people sit. In other
words, there is no assigned
seating – it’s first come, first served.
She will be booking bigger acts and wants to start assigning tickets, but
she knows that this will take
a lot of organizing. She’s asked you to help her by creating a database that
will track sales and
seating for her concerts.
Details: The database you are to create needs to take the following into
account:
• There are many performers that play at the hall. They could be performing
for one night or
many nights.
• A customer can purchase one or many tickets for an event (for example,
buying five tickets,
one for themselves and four for their pals). Each ticket is assigned a seat
• There are three sections in the concert hall: “Orchestra front†(the most
expensive),
“Orchestra main†(on the main floor, but further back, so less expensive),
and “Balcony.â€
Each section has a different price, which depends on the performer (it costs
more to get
tickets in for the Rolling Stones than for Hilary Duff, for example).
• The seats are all numbered from 1 to 100 in each section (NOTE: You don’t
have to enter 100
tickets for the purpose of the test – you can shrink this down to something
smaller, like five (5)
tickets per sections to demonstrate your database)
I currently have a table to hold the different sections, each concert,
performer names, and customer info, and a ticket table that currently only
holds a seat number. I've basically deleted everything I've tried and gone
right back to the basics. My main problem is the price, I can't seem to get
the correct price listed (it has to be based on the performer and the section
the seat is in). Everytime I think it's going to work, when using a lookup
wizard, it lists all the prices(which I don't want it to do).
My thoughts are that I need a price table that holds a foreign key from the
performer and section tables, and a price listed accordingly. But when I do
this and I put a price foreign key in the ticket table (using a lookup
wizard), it shows every single possible price, which would be acceptable if I
could list the performers name and section beside it(which I haven't been
able to do since all I can get beside it are the actually key values and not
actual useful data)
Hopefully this explnation made even a little bit of sense. Could anyone
please send me in the right direction? I would appreciate it so much. Thanks.
a fundamentals course so please excuse if the answer is rather obvious).
Here's the scenario that I'm working on. Sorry for how long this is, and
hopefully this is the right section to put it.
Sally Sniggins runs a small concert hall that promotes local Jazz bands.
Currently, she handles all
the ticket sales by hand, and doesn’t track where people sit. In other
words, there is no assigned
seating – it’s first come, first served.
She will be booking bigger acts and wants to start assigning tickets, but
she knows that this will take
a lot of organizing. She’s asked you to help her by creating a database that
will track sales and
seating for her concerts.
Details: The database you are to create needs to take the following into
account:
• There are many performers that play at the hall. They could be performing
for one night or
many nights.
• A customer can purchase one or many tickets for an event (for example,
buying five tickets,
one for themselves and four for their pals). Each ticket is assigned a seat
• There are three sections in the concert hall: “Orchestra front†(the most
expensive),
“Orchestra main†(on the main floor, but further back, so less expensive),
and “Balcony.â€
Each section has a different price, which depends on the performer (it costs
more to get
tickets in for the Rolling Stones than for Hilary Duff, for example).
• The seats are all numbered from 1 to 100 in each section (NOTE: You don’t
have to enter 100
tickets for the purpose of the test – you can shrink this down to something
smaller, like five (5)
tickets per sections to demonstrate your database)
I currently have a table to hold the different sections, each concert,
performer names, and customer info, and a ticket table that currently only
holds a seat number. I've basically deleted everything I've tried and gone
right back to the basics. My main problem is the price, I can't seem to get
the correct price listed (it has to be based on the performer and the section
the seat is in). Everytime I think it's going to work, when using a lookup
wizard, it lists all the prices(which I don't want it to do).
My thoughts are that I need a price table that holds a foreign key from the
performer and section tables, and a price listed accordingly. But when I do
this and I put a price foreign key in the ticket table (using a lookup
wizard), it shows every single possible price, which would be acceptable if I
could list the performers name and section beside it(which I haven't been
able to do since all I can get beside it are the actually key values and not
actual useful data)
Hopefully this explnation made even a little bit of sense. Could anyone
please send me in the right direction? I would appreciate it so much. Thanks.
