Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Database Design / December 2004

Tip: Looking for answers? Try searching our database.

combining several activities w one contact?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Beth - 27 Dec 2004 14:11 GMT
I am trying to put together a volunteer database for my church.  There are
several catagories for volunteer work, ie., Fellowship, Building & Grounds,
Worship, etc.  Within each of these catagories, there are several specific
volunteer opportunities.  For example:  Fellowship has: Serving meals,
Greeting, New Member Sponsors, Harvest Feast, etc.

Although I know the basic of Access, I cannot seem to figure out how to
structure this data base into tables and how to link them to the master file,
which has no primary key as there are duplicates and blanks spaces in some of
the items.

Any suggestions?
Jack MacDonald - 27 Dec 2004 14:47 GMT
Break the problem into three components: defining the work categories,
cleaning up the existing data, and assigning the people to categories
(... or categories to people...)

First, the work
You should make two tables. Each has an autonumber Primary Key, and
each has a "description" field. One table for the general categories,
and one table for the specific opportunities.

tblWorkCategory
- WorkCategoryID   autonumber, PK
- WorkCategoryDescription   text

tblWorkSpecific
- WorkSpecificID   autonumber, PK
- WorkCategoryIDfk  long Integer, foreign key to WorkCategory
- WorkSpecificDescription   text

These tables are related one-to-many -- each WorkCategory can have
many WorkSpecifics. Ultimately, you will assign each person with one
or mor WorkSpecificID's

Two - Clean up the existing database. You will need to do some of this
manually, and perhaps some with the Find Duplicates query wizard. I
would also copy the structure into a new table, then add an autonumber
field named PeopleID, then import the existing data.

Three - assign people to work specifics. I imagine that you will want
a many-to-many relation between these two tables in order to allow
each person to assume more than one responsibility. Accordingly, you
require a junction table.

tblPeopleWorkSpecific
- PeopleWorkSpecificID   autonumber, PK (optional, but my preference)
- PeopleIDfk   long Integer, foreign key to people table
- WorkSpecificIDfk  long integer, foreign key to WorkSpecific table

Create a composite, no duplicate index on PeopleIDfk and
WorkSpecificIDfk to prevent one person from being assigned twice to
the same responsibility.

A for entering the data, the conventional way is to create a form for
people, with a subform for their responsibilities, based on the
tblPeopleWorkSpecific table. You will enter one or more
WorkSpecificIDfk for each person using a combo box whose recordsource
is driven by tblWorkSpecific.

>I am trying to put together a volunteer database for my church.  There are
>several catagories for volunteer work, ie., Fellowship, Building & Grounds,
[quoted text clipped - 8 lines]
>
>Any suggestions?

**********************
jackmacMACdonald@telusTELUS.net
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security
Beth - 27 Dec 2004 15:09 GMT
Thank you so much.  I will try your ideas first.  I may have to talk with you
again.

Beth

> Break the problem into three components: defining the work categories,
> cleaning up the existing data, and assigning the people to categories
[quoted text clipped - 60 lines]
> remove uppercase letters for true email
> http://www.geocities.com/jacksonmacd/ for info on MS Access security
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.