Introductory table building question

[NoviceNana]

I have a fairly basic question about table design. I'm building a
database that has 1 main table which is a list of client names. The
clients can get 3 different services and then they are discharged from
the program. My client table is my main table but I have 3 different
tables for the 3 types of services.

So currently the main client table has client names and general
information and information about discharge. I have one table for
each of the other services and they are on 3 different forms where the
main form links to the main client table and the subform links to one
of the 3 service tables.

Is this a good way to do this, or is it better to combine the
information about the 3 service types into one table so there's only
the main client table and then the services table that comprises all
three services.

Thanks for any advice.

 

[BruceM]

Three tables for services is not an effective design. How exactly you would
proceed depends on what you mean by Services. That is, does a service
comprise a lot of diverse information, or is it described with just a word
or phrase? If the services are Brakes, Tires, Exhaust, you could pick one
of those words from a list and store it in a Services table. If the
services are 15,000 mile service, 30,000 mile service, and 60,000 mile
service, each one of those has its own list of requirements. In that case
you would have a Service record consisting of mileage, date, and other
general information about that particular service. In another table,
related to the Service table, you would have ServiceDetails. I won't go too
far down that road since I don't know your needs.
I realize you aren't talking about automobiles, but since I don't know the
context I thought it would be simplest if I provide one.