database design question

[Chris Nebinger]

Let me add one more to the pile...

Project_Services (the services that we provided on the
project, all true/false)

So, you are planning one record for each project, with a
True/False field? A better approach would be:


tblServices (all services we provide)
ServiceID
Service

tblProjectServices
ProjectNumber
ServiceID

Projects
ProjectNumber



Chris Nebinger

-----Original Message-----
Hi all,

I'm trying to design a database to store project

information for construction projects, to be used for
marketing purposes. My experience with Access is pretty
limited, and as such, I'm having trouble evisioning a
proper table design for the database.

The problem comes when I consider contacts for each

project. I'd like to be able to have a single table of
contacts and assign project roles as appropriate. The
reason that I'd like to do this is contacts may play
different roles on different projects (i.e., a client can
also be a tenant or a building owner, etc.). If I build
separate tables for each contact role on a project (I've
got 13 different roles that I want to assign a contact
to), I'd end up with duplicate contacts in different
tables.

So far, I've set up the following tables:

Project_Physical (all the physical attributes of the project - location, size, etc)
Project_Services (the services that we provided on the project, all true/false)
Project_Costs (costs for various pieces of the project)

Can someone advise me on how to handle the contacts in

this situation? Can I use one contact table and use lookup
tables to do this, or am I going to have to create a bunch
of separate contact tables?

 

[CNC]

Chris,

Thanks for the advice. If I could, I'd like to aks a follow-up question based on your suggestion: If I set up the tables this way, will I be able to use the checkbox control on an input form to select what services were performed on a project? This is why I figured using the T/F in the table was the best route to go, because I wanted to use the checkbox control. I'm also open to other ways of implementing this on an input form, if you can suggest a better idea.

Thanks,
Chris