It is common for some “glitches” to occur when trying to set up any new computer program. Hopefully, you won’t have any problems. If you should, though, please follow the steps below to resolve them.
1) Check and recheck your databases for typing errors.
· Are all the required fields filled in on every page?
· Are all fields filled out as specified in this manual?
· Is all the information correct?
· Print out the Personnel Database Listing Files. It is often easier to spot problems on the printed page than on the database forms in the program. Computers still suffer from the “garbage in -- garbage out” syndrome. A typing mistake in the wrong place can wreak havoc on your schedule.
2) Read this manual carefully. Check the Contents page for any references that may have a bearing on your problem.
3) If you have a problem with the Schedule not coming out like you expected, read Chapter
17, “Scheduling Problems and Solutions” to look for an answer. Also check our online forum at:
http://www.twopaths.com/forum.htm
4) If you received an error message while running CV-Schedule, read Appendix IV, “Error Messages,” to look for a solution.
5) If you are not experienced working with computers and databases, consider recruiting a computer-knowledgeable
person from your congregation or parish to help.
6) If you are still having a problem, please write, and I will do my best to help. There is
no charge for this service. Tech support is available only through our Website at:
http://www.twopaths.com/forum.htm
When you write for Technical Support, I can best help if you:
· Describe the problem you are having in as much excruciating detail as possible.
· Tell what you were trying to do when the problem occurred.
· If you received an error message, copy exactly what it said.
· If you are having scheduling problems with some volunteers, enclose a copy of the Personnel Database Listing File.
· Tell what kind of computer, word processor and printer you are using. What version of Windows does it have?
· Tell what things you have already tried to resolve the problem.