home

PDS

RealmMinistryPlatformPDSACSAccountingGivingConnectShepherdGrowth MethodGo MethodMissionInsiteGatherHeadMaster ChildcareTrust CenterData Governance and Business DocsACST Content Standards
RealmMinistryPlatformPDSACSAccountingGivingConnectShepherdGrowth MethodGo MethodMissionInsiteGatherHeadMaster ChildcareTrust CenterData Governance and Business DocsACST Content Standards

What would you like to know more about?

Show Contents

thumbnailPDS

Ledger/Payroll User Guide

Fix Data Discrepancies

You can verify that your program does not contain discrepancies. Program and data files can develop discrepancies as a result of improper system shutdown, operating system failure, hard drive failure, computer virus infection, network failure, or other computer complications. To minimize this risk, back up your data regularly.

Warning: This process can repair some small problems with the data. If severe discrepancies exist, you can restore data from a recent backup. If this happens, however, all information entered since the last backup is lost.

Employee view only:

Note: Can't run fix? If you cannot run the Fix process in Church or Formation, you can delete or move the Action.PX file. If you cannot run fix in Facility or Ledger, delete the City.PX file. Then, you should be able to run fix.
Tip: Try Test Mode. Sometimes, running the Fix process while in Test Mode can help solve issues better.
Running the Fix process will correct the following errors:
  • Clicking on the Dashboard and the program freezes – First, try resetting the INI file. If that doesn't work, run fix.
  • A component named Year Index already exists – Run fix with the Reindex Tables option selected.
  • In CO or FO, batch numbers are being reused – At the end of fix, select Yes to reset the next batch number to a higher value.
  • In LP, a component named VenAlphaOrder already exists – Run fix with the Reindex Tables option selected.
  • In LP, a component named DueDateIndex already exists – First, check permissions and set all to Full Access. If that doesn't work, run fix with the Reindex Tables option selected.
  • In FS, a component named PkgIndex already exists – Run fix with the Reindex Tables and Pack Tables options selected. If you need to run the fix outside of the program, delete City.px first.
Running the Fix process will NOT correct these issues:
  • A component named TmpIndex already exists – Send issue to product leads.
  • A component named REIDindex already exists – This is caused when the Formation version is older than the Church version. Roll back the INI file. If you still see the error after that, you can run fix.
  • Index is out of date on qppay tables – Explain to the client that they will lose any unposted batches in the program as we have to replace these tables from the empty folder. If they have a lot of unposted batches, try running fix first. If that works, have them post those batches as they may see that error come back.
  • List Index is out of bounds when printing a report – Close the program completely then go back in.
  • Corrupt Header error – You can try fix first, but most of the time, you'll need to restore from a backup.
  • Program Damaged – You must reinstall the program in a new location.
  • Celeb.db – You may see this after restoring in OnDemand. You'll need to go into the Data folder and remove the Celeb.Xg2 and Celeb.Yg2 files. Once you can get into the program, go to File > Keywords > Member Keywords > Celebrant Names and verify that their celebrant names are still in the program.
  1. On the File menu in your PDS program, click Test / Fix > Fix Data Discrepancies.
  2. If you need to fix the "index out of date" error, select Reindex Tables.
  3. To remove empty space in the data tables, select Pack Tables.
  4. Click Fix Data.
  5. Once the process runs, a summary report displays. Review the report for anything you need to be aware of.
Troubleshooting
Church Office
DioOffice
Formation Office
Ledger Payroll

Last updated: April 7, 2026

Related Articles: