By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,829 Members | 673 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,829 IT Pros & Developers. It's quick & easy.

Structuring question - many attributes per person in table

P: n/a
I have 2 tables built in my database already: A People contact table
- tblPeople (with Primary Key pID); and an Involvement table -
tblInvolvement (with Primary Key InvID).

The Involvement Table includes one record for each possible area of
work in the church. I need a way to input multiple areas of service
per person - basically, to link one pID with multiple InvID, but not
in an exclusive manner.
Nov 13 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Create a form for the People table and a subform on that form for the
Involvement table. Make the Involvement data show in datasheet format.

Read the Access Help for info on subforms and how to make them.

--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQRwHsIechKqOuFEgEQKO7ACg+yOrGyXZI5FjX7RDIEudZe fFTpgAoKNb
07CvvTCSr29x/YgdhdotdtSU
=1/Fg
-----END PGP SIGNATURE-----
Josh Kingcade wrote:
I have 2 tables built in my database already: A People contact table
- tblPeople (with Primary Key pID); and an Involvement table -
tblInvolvement (with Primary Key InvID).

The Involvement Table includes one record for each possible area of
work in the church. I need a way to input multiple areas of service
per person - basically, to link one pID with multiple InvID, but not
in an exclusive manner.


Nov 13 '05 #2

P: n/a
Josh,

How about a people involvement table that looks like:
TblPeopleInvolvement
PInvID
PID
InvID
DateGotInvolved

Build a form/subform where the form is based on the people table and the subform
is baed on the involvement table. You can use the form wizard for this. Check
the LinkMaster and Linkchild properties - they should both be PID.

--
PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
re******@pcdatasheet.com
www.pcdatasheet.com
"Josh Kingcade" <jo**@cocsy.org> wrote in message
news:95**************************@posting.google.c om...
I have 2 tables built in my database already: A People contact table
- tblPeople (with Primary Key pID); and an Involvement table -
tblInvolvement (with Primary Key InvID).

The Involvement Table includes one record for each possible area of
work in the church. I need a way to input multiple areas of service
per person - basically, to link one pID with multiple InvID, but not
in an exclusive manner.

Nov 13 '05 #3

P: n/a
Make that -----

........and the subform is based on the PeopleInvolvement table..........

"PC Datasheet" <no****@nospam.spam> wrote in message
news:Bj*******************@newsread2.news.atl.eart hlink.net...
Josh,

How about a people involvement table that looks like:
TblPeopleInvolvement
PInvID
PID
InvID
DateGotInvolved

Build a form/subform where the form is based on the people table and the subform is baed on the involvement table. You can use the form wizard for this. Check
the LinkMaster and Linkchild properties - they should both be PID.

--
PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
re******@pcdatasheet.com
www.pcdatasheet.com
"Josh Kingcade" <jo**@cocsy.org> wrote in message
news:95**************************@posting.google.c om...
I have 2 tables built in my database already: A People contact table
- tblPeople (with Primary Key pID); and an Involvement table -
tblInvolvement (with Primary Key InvID).

The Involvement Table includes one record for each possible area of
work in the church. I need a way to input multiple areas of service
per person - basically, to link one pID with multiple InvID, but not
in an exclusive manner.


Nov 13 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.