[AccessD] DB Design Question

Larry,

Try the following:

tblCompanyOrg
CompanyID
CompanyName
ETC

tlkpServices
ServiceID
ServiceDesc
ServiceGroupID

tlkpServiceGroup
ServiceGroupID
ServiceGrouDesc

tblCompanyOrgLocations
CompanyOrgLocationID
CompanyID
Address
City
State
PostalCode

tblCOLocationPhones
COLocationPhoneID
PhoneNumber
PhoneComments

tblCOLocationServices
COLocationServiceID
COLocationID
ServiceID
ServiceComments

This is one way of structuring it off the top of my head.

Robert


At 04:12 PM 3/26/2008, you wrote:
>Date: Wed, 26 Mar 2008 15:51:40 -0500
>From: "Lawrence Mrazek" <lmrazek at lcm-res.com>
>Subject: [AccessD] DB Design Question
>To: "'Access Developers discussion and problem solving'"
>         <accessd at databaseadvisors.com>
>Message-ID: <020101c88f83$30fd6620$036fa8c0 at lcmdv8000>
>Content-Type: text/plain;       charset="US-ASCII"
>
>Hi Folks:
>
>I'm working on revising a resource directory consisting of
>companies/organizations and the services they offer, and would appreciate
>any feedback regarding a specific design question I have.
>
>Each company/organization can have multiple locations. Given that the
>locations are currently contained in 20+ separate tables, once for each
>service grouping (EX: dogs, cars, birds), and with specific fields for each
>service, I'd like to resolve the locations into one table, and link out to
>services via a some sort of  relationship.
>
>For example, the "dogs" table might have the additional fields: breed,
>color, weight, while Cars might have: horsepower, tire size, etc.
>
>I'd like to have this system to be as flexible as possible, any hints on how
>to relate those service specific fields to the general tblLocation? Note
>that each location might could have multiple services associated with it.
>
>Thanks ... I'm just a bit foggy today and need a second opinion on this
>problem.
>
>Larry Mrazek