I receive the error 'Program halted. Database error...'

This error is the result of one of two different problems. Either one of PageGate's modules has lost contact with the PageGate database, or there is some corruption in the PageGate database. If the PageGate module that reports this error is running on a different computer than where the PageGate database file resides, chances are you have a network connectivity problem (possible an intermittent one). If the PageGate module that reports this error is running on the same computer as the PageGate database file, there is most likely corruption in the PageGate database. Corruption is caused by one of the following conditions:

1. Abnormally terminating PageGate
- PageGate should ALWAYS be shut down in an orderly manner. PageGate's administration program and ALL of the running PageGate GUI Clients should be exited before shutting down the computer that PageGate runs on. Next, each of PageGate's modules should be set to a 'stopped' state (red in PG Monitor). The PageGate service manager should be stopped by clicking on the pager icon in the Windows system tray and then choosing 'Quit' or 'Stop' from the popup menu. All of the above should be done before shutting down or restarting the computer that PageGate is running on. Not following these procedures can in some cases cause database corruption.

- All PageGate GUI Client programs should be closed by choosing 'File' and then 'Exit' from their menus, or by clicking on the 'X' control on their windows (Note: when NotePager Net is minimized, it appears as a pager icon in the Windows system tray. Be sure not to shut down or restart with it still there.). Not following this procedure can in some cases cause database corruption.

2. Freezing, locking, abnormal shutting down/rebooting, or other hardware failures
- If any computer that is running ANY part of PageGate or its GUI client (NotePager Net) freezes, locks up, reboots, shuts down, catches on fire, etc. without using normal shutdown procedures, in some cases can cause corruption in the PageGate database.

3. Operating system errors
- If computers running ANY part of PageGate (including the PageGate GUI Client) receive errors such as: 'the blue screen of death', general exception errors, processor exception errors, illegal instruction errors, page fault errors, etc., in some cases the PageGate database can become corrupt.

4. Incorrect or out-of-date database support files
- PageGate uses the Microsoft Jet database engine (common with MS Access 97) for data access. If any of the database engine files are out of date (older versions are buggy), corruption can appear in the PageGate database. Please refer to the section 'File version problems' in the 'Troubleshooting' chapter of the PageGate help file for more details.

5. Bad or out-of-date operating system files.
- If PageGate is running on Windows NT, be sure that the NT Service Pack 5 or later is installed on all computers that run ANY part of PageGate or the PageGate GUI Client.

- If PageGate is running on Windows 95 or 98, make sure ALL computers that run ANY part of PageGate or the PageGate GUI Client have the current Windows redirector and OLE files. In particular, there is a serious problem with the redirector shipped with some versions of Windows 95 that will almost certainly cause database corruption. Please refer to the section 'File version problems' in the 'Troubleshooting' chapter of the PageGate help file for more details.