User Support Forum

Hi,

The church is interested in linking familiies together. They would like to be able to show a father and wife with their children and then their grandchildren.


For example John and Mary has a son named Peter and they all attend the same church. Peter marries sue who is the daughter of cliford and diana all of whom attend the same church. In the original membership database it will show John been the head of his household and then Mary and their son. This setup would be similiar for Cliford who would be the household head then Diana and Sue their daugther.

Now that Peter and Sue are married and still attend the church. They have sxi kids and both their grandparents attend the same church. The church would like to reflect that peter is the son of John and Mary and Sue is the daughter of Cliford and Diana and their offspring (Six kids) are related to John & Mary and Cliford & Diana.

Meanwhile the six kids are linked to their parents Peter and Sue. How can this be setup to show that John and Mary has one Son, one daughter in law and six grandchildren, meanwhile Peter and Sue profile reflect that they have six kids. Is there a way to do this to avoid duplicate membership counting, duplicate data input and the family tree structure?

Thx
melloby

Not currently. Ususally what we do is create a separate household and move the personal profiles to that new household.

Hi Neil,

I have a scenarios:

What if I make up a code "Family Tree" and list all the family together. Those persons who are children of the household head and have their own children will be tagged with the code "Family tree" with no envelopes assigned to them. We will then setup the children of the household head that have their own famiiles again, this time with the code "member" to reflect their affiliation with the church.

This way we can run a report by the code "Family Tree" and see all the related family members in the church and then by "member" to reflect the membership of the church.

Their will be duplication of data input, but it will help with the family tree structure.

The other alternative is to use the notes column in the family mailing list module and note the family relations in the church and then print the report with the notes, so that the family structure are identified.

melloby

melloby wrote:Hi Neil,

I have a scenarios:

What if I make up a code "Family Tree" and list all the family together. Those persons who are children of the household head and have their own children will be tagged with the code "Family tree" with no envelopes assigned to them. We will then setup the children of the household head that have their own famiiles again, this time with the code "member" to reflect their affiliation with the church.

This way we can run a report by the code "Family Tree" and see all the related family members in the church and then by "member" to reflect the membership of the church.

Their will be duplication of data input, but it will help with the family tree structure.

The other alternative is to use the notes column in the family mailing list module and note the family relations in the church and then print the report with the notes, so that the family structure are identified.

melloby

The duplication of the records could cause problems when name lookups are done in other modules, such as contributions. Even though they may not have envelopes, thoste duplicate records could cause confusion.

Your idea of using the notes would keep track of the relationships, but it would not be programmatic. That is, you couldn't produce a report with the family grouped together.

I know what its like trying to force a system into doing something its not designed for, more often than not, you wind up with more issues then problems solved.