Help please!!!

[Stibbz]

I have started a new database and just wanted some help with the
relationships and to make sure that I have the right fields in each table??

My tables are:

Hirer/Customer
Customer ID (PK)
Society
Title
First Name
surname
address line 1
address line 2
address line 3
Postcode
Tel No
email address

Bookings
Booking ID (PK)
date booked
date of booking
event title
time slot ID
fee
evening extension
special event
customer ID
fee paid


Time Slot
Time Slot ID (PK)
Date (PK)
Cost
Evening extension cost
Special event cost

If anyone could give me some help I would be very grateful as this is my
first attempt at a basic database.

 

[rba]

Hey Stibbz

I would help if you tell us what you want from these relationships, i mean
what do you want as a end result?

grtz

 

[Stibbz]

I want to be able to send out invoices and produce a booking table each week
showing which slots are booked and which aren't

 

[KARL DEWEY]

A couple of things.
Time Slot field Date seems redundant with Date of Booking in Bookings. You
should not use 'Date' for field name as that is a reserved word in Access.

Are you using a multi-field primary key for Time Slot? If not, you can not
have two primary keys in a table. If you are then you can not use an
autonumber for the field. It needs to be limited to the number of slots in a
given day like 1 or 2 or 3 or 4.

 

[Stibbz]

Well i'm not quite sure what do you think my tables and relationships should
look like??

 

[KARL DEWEY]

Hirer/Customer --
Customer ID – Autonumber (PK)
Society - Text
Title - Text
First Name - Text
Surname - Text
address line 1 - Text
address line 2 - Text
address line 3- Text
Postcode - Text
Tel No - Text
email address - Text

Bookings --
Booking ID – Autonumber (PK)
date booked - DateTime
date of booking - DateTime
event title - Text
fee – Number - Single
evening extension – Yes/No
special event– Yes/No
customer ID – Number – Integer (FK)
fee paid– Yes/No


Time Slot --
Time Slot ID – Number – Integer (limited to maximum number of slots in a
day, some events may have 4 slots but others only one - Used with Date-Time
Slot to form multi-field (PK)
Booking ID – Number – Integer (FK)
Date-Time Slot - DateTime
Cost– Number – Number - Single
Evening extension cost – Number - Single
Special event cost – Number - Single

Relations --
Hirer/Customer - Customer ID – one-to-many with Bookings - Customer ID
One customer many bookings
Bookings - Booking ID – one-to-many with Time Slot - Booking ID
One booking many time slots

 

[rba]

Hello

I completly agree with Karl

best regards