access database design. HEEEELP MEEEEE!!

[stuckboy]

I have been asked to create a database for a uni project. I have created the
follwing 3 tables with these fields.

• Customer number (6 digits)
• Name and address including post code
• Date of season ticket purchase

• Event reference (4 digits)
• Event title
• Date of first performance
• Date of last performance
• Event type (C=Comedy,T=Thriller,M=Musical, P=Pantomime)
• Whether suitable for all the family (logical)

• Booking reference (4 digits)
• Data necessary to establish the customer-event link
• Performance date
• Number of standard price seats
• Number of ‘Old McCawber’ seats
• Number of concession seats (child/senior citizen/student etc.)

I cant seem to form the relationships between the tables. I need to form
them to represent the bookings made by the customer where tblbookings (2nd
table) forms the link table?

Also I have to create the following query which I dont have a clue where to
start?
Create a query, called qryTotalSeats, which will select the customer surname
and post code, the title of the event and the date the theatre was attended
for all those customers who booked 6 or more seats for a given performance
over the last six months. You will need to generate the total number of
seats using a calculated field called TotalNum. (Hint: you will need to
make use of the Date() function and other date related functions in the Query
By Example grid.

Any help would be amazing thanks

 

[Jeff Boyce]

You'll find folks here a bit reluctant to do your homework for you.

You might want to remember that relationships between tables requires a way
to tell which record is the "parent" and which is the "child". Check up on
the topic of "foreign keys".

--
Regards

Jeff Boyce
www.InformationFutures.net

Microsoft Office/Access MVP


Microsoft IT Academy Program Mentor
http://microsoftitacademy.com/

 

[Gina Whipp]

StuckBoy,

While I agree with Jeff regarding this being homework. I will tell you
this, you need to get out that pencil and paper (and a BIG eraser) and fix
your tables, ie: Customer Information should be just that. Storing Date of
Season Ticket Purchase is going to be a problem and makes the table only
good for one season, if that. Suppose I, the Customer, purchase Season
Tickets for me AND the guy next door but I don't do it on the same day? And
that's just the first table.