Prev: #Name?
Next: Attendance Tracking
From: Lisa on 4 May 2010 16:16
Hi All, I am also creating a church database. I was doing the same thing. Head of House table and dependant table. It was working fine but I read somewhere that for greater normalization of my database i might want to take another approach. Namely a complete member table and another table that has adresses ( which tend to be unique to the household) But I'm getting caught up in how the dependants can be connected to this unique address table primary key.

Am I thinking about this all wrong? Should I go back the master /dependant tables?

Thanks for any help.
Lisa Missenda



JD Steiger wrote:

Creating a membership database
10-Feb-10

I am trying to create a membership database for a church.

I need to have all members entered into the database, then for the members I
need to have their spouse name and anniversary, and the names of their
children. I am trying to get a subform for each of these into the main form,
but when I try to use it it just shows the spouse in the first spot as the
spouse for every record.
I need to lock or bind this information to each "Master" form.
So that joe smith at 123 anyplace somewhere usa will show his spouse and
children while joe smith at 456 somewhere anyplace usa will show his spouse
and children also the spouse's page (jane smith) will show joe smith as her
spouse with their children.
I would also like to hyperlink the spouse name so that if you click it their
record will be pulled up.

Anyone that can help me with this endeavor would be greatly appreaciated.

Previous Posts In This Thread:

On Wednesday, February 10, 2010 8:50 PM
JD Steiger wrote:

Creating a membership database
I am trying to create a membership database for a church.

I need to have all members entered into the database, then for the members I
need to have their spouse name and anniversary, and the names of their
children. I am trying to get a subform for each of these into the main form,
but when I try to use it it just shows the spouse in the first spot as the
spouse for every record.
I need to lock or bind this information to each "Master" form.
So that joe smith at 123 anyplace somewhere usa will show his spouse and
children while joe smith at 456 somewhere anyplace usa will show his spouse
and children also the spouse's page (jane smith) will show joe smith as her
spouse with their children.
I would also like to hyperlink the spouse name so that if you click it their
record will be pulled up.

Anyone that can help me with this endeavor would be greatly appreaciated.

On Wednesday, February 10, 2010 9:34 PM
John W. Vinson wrote:

The way I have done this is to have a "Household" table related one-to-many to
The way I have done this is to have a "Household" table related one-to-many to a
"Members" table. The address is stored in the household table; it lets you
search for a member and will bring up a form with that member's household on a
subform.

If you would like a free, open code copy of the database, drop me an email at
jvinson <at> wysard of info <dot> com.
--

John W. Vinson [MVP]

On Thursday, February 11, 2010 12:56 PM
Steve wrote:

Open the main form in design view. Select the subform control.
Open the main form in design view. Select the subform control. Open
properties and go to the Data tab. Set the Linkmaster and Linkchild
properties to MemberID. The subform will now only show the data in the
subform for the member in the main form.

If you want help with yur database, I can help. I provide help with Access,
Excel and Word applications for a very modest fee. I can get your database
up and running quickly for a very reasonable fee. Contact me to begin using
your database soon.

Steve
santus(a)penn.com

On Thursday, February 11, 2010 1:12 PM
Stop$teve wrote:

Remember ???
Remember ???

"I judiciously chose who to offer fee-based help to based on whether it appears highly unlikely that the poster will get a solution
from the newsgroup."


Get lost $teve. Go away... far away....

Again... Get lost $teve. Go away... far away....
No-one wants you here... no-one needs you here...

This newsgroup is meant for FREE help..
No-one wants you here... no-one needs you here...
OP look at http://home.tiscali.nl/arracom/whoissteve.html
(Website has been updated and has a new 'look'... we have passed 11.000 pageloads... it is a shame !!)

Arno R

On Thursday, February 11, 2010 1:58 PM
John W. Vinson wrote:

Sorry, Steve, I have already sent them my FREE church membership database.
Sorry, Steve, I have already sent them my FREE church membership database.

Some of us have ethics.
--

John W. Vinson [MVP]

On Thursday, February 11, 2010 3:26 PM
John... Visio MVP wrote:

Stevie is our own personal pet troll who is the only one who does
Stevie is our own personal pet troll who is the only one who does not
understand the concept of FREE peer to peer support!
He offers questionable results at unreasonable prices.

These newsgroups are provided by Microsoft for FREE peer to peer support.
There are many highly qualified individuals who gladly help for free. Stevie
is not one of them, but he is the only one who just does not get the idea of
"FREE" support. He offers questionable results at unreasonable prices. If he
was any good, the "thousands" of people he claims to have helped would be
flooding him with work, but there appears to be a continuous drought and he
needs to constantly grovel for work.

John... Visio MVP


Submitted via EggHeadCafe - Software Developer Portal of Choice
WPF Binding Beyond the Limitation of Name Scopes
http://www.eggheadcafe.com/tutorials/aspnet/ef583104-e507-491d-b05f-49faac8854c8/wpf-binding-beyond-the-li.aspx
From: John W. Vinson on 4 May 2010 17:01
On Tue, 04 May 2010 13:16:44 -0700, Lisa Missenda wrote:

>Hi All, I am also creating a church database. I was doing the same thing. Head of House table and dependant table.
It was working fine but I read somewhere that for greater normalization of my
database i might want to take another approach. Namely a complete member
table and another table that has adresses ( which tend to be unique to the
household) But I'm getting caught up in how the dependants can be connected to
this unique address table primary key.

My church membership database (you're welcome to a free copy if you're
interested, just email me at jvinson <at> wysard of info <dot> com) has a
Families table related one to many to a Members table:

tblFamily
FamilyID <autonumber primary key>
SortName <last name or other name for sorting>
DisplayName <e.g. "Mr. & Mrs. Joe Jones", "The Benson Family", "Tim Roberts
& Mary Jones">
<address, phone, email, etc.>

tblPeople
MemberID <autonumber primary key>
FamilyID <Long Integer fk to Families>
MemberNum <optional "giving envelope number">
LastName
FirstName
MiddleName
Suffix

There's no "head of family" - everyone in the family is on the same level.

I included a "MoveOut" button on the Members subform which takes a person and
creates a new record in tblFamilies and assigns them to that new FamilyID
(e.g. when a child moves out on her own).

--

John W. Vinson [MVP]
 | 
Pages: 1
Prev: #Name?
Next: Attendance Tracking