Tables

[Pauldohert]

If I had a db that needed to record vasltly differant services offered to cutomers

ie

hire of equipment
sale of goods
attendence on a training course

if I was making a database for each of these separately no doubt the booking table for each service would look very differant as very differant info is need for each service.

If I was making a db with all three of these as part of the system - would I stay with 3 differant booking tables or somehow combine them into one?

 

[Pauldohert]

Thanks Pat.

 

[TaiChi56]

I would make each of your examples a table. So you would have "Hire of Equipment" one table, "Sale of Goods" and "Attendance on a training course" each their own table. You would then link them as needed. For example, "sale of goods" would have a relationship to your customer table, attendance on a training course would have a relationship to your employee table, so forth.

I would suggest using an E-R diagram and draw it out before starting your application. Hope this helps.

If I had a db that needed to record vasltly differant services offered to cutomers

ie

hire of equipment
sale of goods
attendence on a training course

if I was making a database for each of these separately no doubt the booking table for each service would look very differant as very differant info is need for each service.

If I was making a db with all three of these as part of the system - would I stay with 3 differant booking tables or somehow combine them into one?