Contribution Statements via E-Mail
Posted: Mon Oct 10, 2005 7:40 pm
Our church plans to start sending contribution statements via e-mail to those who have agreed to accept electronic statements vs. hard copy. We have polled the congregation and, to date, only a small percentage has agreed to receive statements via e-mail. For those who have not yet agreed, we must ensure that membership records are properly coded so statements aren’t inadvertently e-mailed to those who don’t want e-mailed statements.
The membership module of our PowerChurch data base is maintained by the church secretary who informs us that most membership records are presently coded for members to receive statements by e-mail, i.e. the authorization check box on most membership records is already checked. We believe that these checkboxes should initially be unchecked, and the secretary should apply checks to boxes only after receipt of specific authorization from each church member.
Question: Is there an efficient way to uncheck all authorization boxes (statements by e-mail) on membership records, i.e. via a global command? We are presently attempting to uncheck all boxs by stepping through the membership records one by one. At three mouse clicks per record (“Next” button – checkbox – “Save” button), this will require a over 6000 mouse clicks.
The membership module of our PowerChurch data base is maintained by the church secretary who informs us that most membership records are presently coded for members to receive statements by e-mail, i.e. the authorization check box on most membership records is already checked. We believe that these checkboxes should initially be unchecked, and the secretary should apply checks to boxes only after receipt of specific authorization from each church member.
Question: Is there an efficient way to uncheck all authorization boxes (statements by e-mail) on membership records, i.e. via a global command? We are presently attempting to uncheck all boxs by stepping through the membership records one by one. At three mouse clicks per record (“Next” button – checkbox – “Save” button), this will require a over 6000 mouse clicks.