Hairdressers Appointment Booking Database AND WILL THIS IDEA WORK OR NOT

Hi
Can some help me me entities for my hairdressers appointment booking
database. Because i have no idea what tables i will need and what they will contain.

AND

In my hairdressers appointment booking database how will i make appointments, do i need like tables with dates and times or something. because each hair styler does a certain thing, so if a customer comes and says they want feathers, i will assign them to a partcular hair styles. How will i do this.

Please help

Thank you

Have you attended your CS database class?!

I dont go to CS datavase class because i dont have one. This datbase is for my A Levels course and i need help on it.

What work have you done for it so far?
It feels as though you're asking us to do all your work.

What are some table schemas you've developed thus far?

Well so far i have a the customers table: customer ID, Name, address, contact info, age, gender.
A stylist table: Stylist ID all as above but with treatment ID
A treatment table: Treatment ID, Treatment name, description, price , discount
Booking: booking ID, customer ID, Treatment Id, Stylist ID, Date, Time.
Maybe Payment: Payment Id, Booking Id, Amount Due, Paid?

I am not sure if that is right, should i put the payment table, and if so, are the contents right. Also the booking table, is the field names fine or will i need to add something. And how would i normalise my data.

The only work we have done is, finding the table we will need and starting designing them.

Thanx

What's a treatment?
Is that like a skill?
Can a stylist have more than one treatment?
Can a customer have multiple treatment's done in one booking?

Yeah the treatment is like a skill, eg tinting and so on
And the stylist can have more than one treatment and the customer can have multiple treatments done, but not in one booking, they will have it on different days and time.

If a stylist can have more than one treatment, I suggest taking 'treatment_id' out of the stylist table.

Stylist and Treatment is like a many to many relationship.
In this case, we build a bridging table to link the two together.
This table could be named something like Stylist_Treatment, and simply contain the Stylist ID and the Treatment ID.

this way, if you want to find all the Treatments that a stylist can do, grab all from Stylist_Treatment where stylist id is [whatever]. If you want to find which stylists can perform a single Treatment, grab all from Stylist_Treatment where treatment id is [whatever]

other than that, your tables look okay.

Thanx alot for that, so do u think i should have a payment table. Because my teacher told me i need max of 4 to 5 tables. And by making the stylist_treatment table i will have 6 tables. And i think stylist_treatment table is actually a good idea.

And do you know i would of normalisaed my data to get these tables.

if there's only ever one payment per booking, then i suppose you could put the payment information in the booking table.
Your best bet is to discuss this stuff with your teacher; everybody designs databases different ways.

Thanx for all your help. But i have one question. You know when i make my form for booking. How will i do it because i want to link each booking to a hairstylist. And they can not have a booking on the same time and day. So how will i get around booking treatments and linking the booking to the stylist.

For eg. Customer 1- wants highlights on 15/3/2005 and time 9.00am
Customer 2- wants blow dry on 15/3/2005 and time 10.00am
And stylist X does both treatments. So how will i order the time for the stylist so no customer has the same booking on the same day and same time. but a booking can be on the same day but different time of course.

Is it necessary to choose the hairstylist?

Why not simply choose the treatment, date and time. Then have the system decide which stylist to assign. If none are available, then return that to the person filling out the form.

I find dealing with Date and Time (and the idea of conflict) one of the more difficult things to program in this type of system.
I'm not sure the best answer =)