Problem: There are spaces in the accounts that have been set up for either checking and or your savings accounts.
Solution:
1) Back up your data. Refer to Chapter 19 in your manual
2) Go to your table view for the checking account and try to edit your account. If you are using ChurchPro2003 go to step 3. If yo are using ChurchPro2004 and above go to step 6.
3) Go to the Tools module from the Main Menu. Click on the other tools tab. Click on the repair icon.
4) Once in the Table Repair Utility, you will need browse to find the ‘ACCOUNT1’ in the browse window. Click on ‘ACCOUNT1’. Click open.
5) You should get a message when the table has finished repairing. At this point close ChurchPro, reopen, check your accounts.
6)ChurchPro2004 and above users may or may not have the Table Repair Utility on their disk. If you don't you may download from our home page. Save it to a place that will be easy to find. Once saved, you will need to unzip and extract the files to your ChurchPro working folder. Once the files are extracted, read the Table Repair Utility.pdf instructions first. Please follow the directions.

Problem: When Launching Paradox, you receive the error "could not initialize BDE". This error can occur after uninstalling older version of Paradox from the system. The uninstall routine may have removed the Borland files from the system or Borland keys from the registry. It can also happen if there are Paradox lock or net files remaining on the system. There is a third possibility: the registry entry that provides the location of the BDE files has incorrect paths or is not there at all.

Solution:
1. To fix the first possibility, reinstall the Database Engine by running a Custom install and select only the Borland Database Engine. This will restore the missing BDE.
2. For the second possibility, do a search for P*.lck and P*.net files and delete any that are found with the name Paradox or pdoxusrs.
3. Restart Paradox.

Problem #1: The application terminated abnormally and left .LCK and .NET files floating around.
Solution #1: Close all BDE applications and search for and delete the following files at the file server and all workstations: PDOXUSRS.NET, PDOXUSRS.LCK, PARADOX.LCK

Problem #2: Multiple workstations accessing the same table are referencing the NET DIR differently.
Solution #2: The NET DIR (in BDEADMIN or your application's NetFileDir parameter) should be configured using the exact same path (only the drive letter may differ) to reference the NET DIR on all workstations. Using UNC for the path may help with consistency and thus help resolve this error.

Problem: This error was triggered due to corruption of Paradox status and toolbar configuration files.
Solution:
1) Close Paradox
2) Search for pdx_en*.cfg files through your search or find program. Once found rename or delete all files found.
3) Re-start Paradox.

Problem: Paradox 9 Runtime will intermittently cause a General Protection Violation when forms containing ObjectPAL are run repeatedly.

Solution:
Download the Service Pack that will update the prform32.dll that corrects this issue.
1. Go to the Corel download site.
2. Click on Appropriate Service Pack and save to your hard drive.
3. Close all Corel applications.
4. Run the executable file that will update several files. make sure that all instances of PRFORM32.DLL on your system have been updated to version 9.00.738

By default, these are located in C:\Program Files\Corel\Paradox 9 Runtime\Programs (for Runtime)

5: Download PRFORM32.DLL and copy to the above folders

Problem: A table has become corrupted.

1. Incorrectly setting the LOCAL SHARE property.
Set LOCAL SHARE to TRUE on all workstations

2. Error transmitting data from the workstation to the server (bad network hardware: cable, card, hub, etc)

3. Private directory set to local or remote (not shared) directory

4. All workstations point to the same shared directory for the NET DIR settings

5. Problem with opportunistic locking Windows NT/2000 ONLY: Try turning off opportunistic locking in the Windows NT registry: See Microsoft Articles Q129202 and Q296264

6. Improperly closing files - such as due to loss of power or restarting a workstation or the server without closing files first may cause this problem. Paradox tables are not designed to withstand such behavior. If this is a possibility in your environment, we recommend you use a Client Server database that can recover from such conditions

7. Extremely large numbers of indexes, especially involving Referential Integrity can cause this problem We recommends using a Client Server

Solution #1: There are several known situations that can cause this to happen. Here are some of the more popular causes.
1) Back up your data. Refer to Chapter 19 in your manual
2) Go to the Tools module from the Main Menu. Click on the other tools tab. Click on the repair icon.
3) Once in the Table Repair Utility, you will need browse to find the ‘ACCOUNT1’ in the browse window. Click on ‘ACCOUNT1’. Click open.
4) You should get a message when the table has finished repairing. At this point close ChurchPro, reopen the module your were having trouble with.

Solution #2: Use this solution when the Main Menu is the module with error. If you are networked you need to go to the ‘server’ to perform this operation
1) Clear the error from the screen, typically you have to do this twice. You will have only the ‘Paradox Runtime’ screen open.
2) Go to the ‘Paradox Runtime’ menu in the top left corner of the screen. Click on the ‘Project Viewer’ icon
3) In the Project Viewer dialog box, the working directory or database shoud read C:\ChurchPro\ChurchPro200X depending on your software version.
4) In the icon box to the left in the ‘Project Viewer’, click on Scripts. Click on Tools.SSL
5) The Tools Menu will come up. Click on the other tools tab. Click on the repair icon.
5) Once in the Table Repair Utility, you will need browse to find the ‘MAIN’ in the browse window. Click on ‘MAIN’. Click open.
6) You should get a message when the table has finished repairing. At this point close ChurchPro, reopen ChurchPro.

Problem: Your application (or another BDE application) has exhausted the memory available to the BDE.
Solution:
1) Close all BDE applications.
2) Find the program, BDE Administrator. This is usually in your Control Panel.
3) Run the BDE Administrator and click on the Configuration tab.
4) There should be an item in the treeview on the left side called "Configuration". If it's not expanded, expand it.
5) Next, expand the System entry below it. Under System, select INIT.
6) In the right-side window, find the entry called "SHAREDMEMSIZE". Change this value to 2048 or 4096.
7) Next, click on the word "Object" in the main window's menu bar, and select Apply.
8) Answer "OK" to the confirmation to "Save all edits...".

You can now try to start your application again. If you still have trouble running the application and you are running Windows NT or Windows 2000, follow the same instructions above, but this time leave the SHAREDMEMSIZE property at 2048 or 4096, and change the SHAREDMEMLOCATION property to "0x5BDE". Then apply the changes as before, and retry your application. If you still receive the same error, try changing SHAREDMEMSIZE to 8192. If the error continues to persist, you can also try "0x6BDE" for SHAREDMEMLOCATION. If the error still continues to persist, you can also try other values for SHAREDMEMLOCATION.

Problem: When trying to print a report or query, the following error occurs:
"Print interface setup error. PFPS Initialize error."

Solution:
1. Run pfreg.exe from the programs subdirectory under Paradox 9.
2. Click Unregister, then click Register.
3. Restart Paradox.

Problem:"Printer fonts have changed" error loop while trying to run and print a report

Solution:
There are several possible causes for this error and/or other printing problems.

1) You are not printing to the default printer. Change the default printer to the printer that you want to print the report on and then restart Paradox.

2) The problem could be a print driver problem. Try upgrading to the latest driver for your printer.

3) Paradox may be having trouble using the driver if the driver has a more recent release date than Paradox. Try downgrading the printer driver to an older version

4) If your printer is on the network, try installing and running the printer locally to the workstation to see if the problem lies within the network. It may be a result of the network path the current printer driver is set to

Problem: Reports print extra blank page in between each normaly printed page of the report.
Solution:
1) If printing from Menu: File | Print. Change "Overflow handling" to "Clip to Page Width" in the printer dialogue box.

Change here

Problem: When trying to initialize Paradox 9, the user gets an error - GPV in CRLUI90.DLL - Runtime error 216

Solution:
1) Copy the pdxrwn32.exe file from the ChurchPro CD (or WordPerfect 2000 Pro CD) to the hard drive.(C:\Program Files\Corel\Paradox 10 Runtime\Programs) Overwrite the existing copy of this file.
2) Download the file from ChurchPro -pdxrwn32.exe go back to solution 1.

Problem: When installing Paradox 9, errors such as "A required source file was not found", may be encountered when loading in a Windows O/S ‘95, ‘98 amd ME enviroment.

Solution:
The CD-ROM drive may be running in MS-DOS Compatibility Mode. To verify this in Windows 95, 98 and ME, right click on the My Computer icon and select Properties. Click on the Performance tab. If either File System or Virtual Memory are set to 16-bit, this may be what's causing the problem. Updating the CD-ROM drivers to 32 bit should also fix the problem. Contact the CD-ROM manufacturer to obtain the drivers.

Problem: A table has exceeded one of the internal BDE or Paradox file limits.
Solution: You have probably hit the limit on the number of blocks that a Paradox table can contain (65535 blocks). In order to store additional records in the file, you'll need to increase the table's block size to allow each block to hold more records. You can increase the block size of a table by running the BDE Admin and change the block size for the Paradox driver to a revised number. Legal block sizes are 1024, 2048, 4096, 16384 and 32768. If your block size is larger then 4096 then you must also change level to be at least 5. Finally, create a new table and batch move your data from your old table to your new table.

Problem: After applying Service Pack 2 for WPO Office 2000, right-clicking files in Windows Explorer results in the following error message "Unable to load language resource DLL"2

Solution:
Copy the SHLWP9EN.DLL from the WPO 2000 CD (\corel\config\system), to the following folder on your hard drive:

Win 95/98 C:\ WINDOWS\SYSTEM

Windows NT C:\WINNT\SYSTEM

IF SHWP9EN.DLL is not on your Paradox 9 CD, you can download it here.