Deceased Members on Birthday/Anniversary Report

[Leigh]

Members whose personal status in personal profiles is "deceased" are on the birthday/anniversary report. How can this be fixed?

[Zorak]

When running that report, click the ALL button next to Personal Status and uncheck anyone that you don't want to be included (deceased, visitors, etc.)

[RevWJones]

I have a similar concern. I have configured my Today screen to show birthdays and anniversaries each time PC v11.5 opens. One of the things that is so annoying is to see the birthday of our deceased. We print every person's birthday in our monthly bulletins but we exclude the deceased and in-active ones from our reports. But I used the Today screens to know who to make a call to today. I have gone so far as to uncheck the "Include in Membership Module Reports" on the Family "Profile" but this doesn't work for the Today screen. Also I am cautious about this because it only works if no one else in that family are actively involved in our church.

Please, is there any way to prevent the deceased birthdays from showing on the Today screen without removing the birthday? I know I could type them into the Notes section and maintain that information but I would prefer to accomplish this systemically?

Thanks
Wardell

[tborgal]

I played around with this in the Today screen for a bit and though I could not reproduce the problem Wardell has I did have problems with it. In my case if I de-select Deceased not only did the deceased not show up but all the names that have <none> in Personal Status did not show up either. If I clear all selections and only select <none> none of the <none> are listed. I could not get them to list until I selected Deceased. This is in the birthday list. Looks like a bug to me but maybe I am missing something.

[RevWJones]

Tom, thanks for your response. I probably should have started a new topic. I am referring to the Today Screen only; not the reports. There's gotta be an option to remove the deceased from ALL lists if desired. I'll check the documentation. Again, thanks.

[Zorak]

Sorry we didn't get this post updated. We have tested this and were able to recreate the problem you are having with the <NONE> selections. It has been written up as a bug and will be fixed in a Maintenance Release.