Check Reader - check information

[CranfordUMC]

I am the church treasurer running PC+ Version 11 and am considering getting a check reader from PC+ for entering contributions. I work from home and maintain the Contribution and Accounting modules on my PC. The Membership module is maintained on the church computer by the church secretary. I keep both computers in sync by doing backups and restores of each module since there is only one master copy of each. My question: In which module within PC+ is the check information stored and tied to the envelope number? If the check information is stored in the Contribution module I am fine. If the check information is stored in the membership module it could pose a problem since I may not have a current version on my PC. I have tried exporting the system to an Access database but have been unable to locate where the checking information is being stored.

[Zorak]

The account information is stored in a table called COCHECK. It is encrypted. You won't be able to access it directly, only through the Check Reader screen in PowerChurch.

[CranfordUMC]

This is great since the information is stored in the Contribution module which is totally under my control.
The table COCHECK must be created during the installation of the check reader since it does not exist now.

Thanks much for the help.

[Zorak]

Sorry... I was wrong (that's what I get for answering from memory instead of looking it up!)

It is COSCAN, not COCHECK

[wms7328]

Speaking from experience in trying to maintain files on two separate computers and keeping the data synced. This is very difficult and requires very careful coordination to keep from loosing data that was entered on one system and then overwritten when an restore was done from other computer. I tried this for about a year and was constantly finding errors that were introduced because either the membership files were changed by office staff or contribution files were changed by treasurer. Once I got both of these folks using same master file, we have several computers on network, all the problems disappeared.

Would just suggest that you consider getting networked together so that everyone is working from same data base all the time.