In order for ReminderPro to function, data is stored in tables in the ReminderPro directory.
Each table stores different kind of information. But a table is just a file, and it can become damaged. If a table is damaged, the function it applies to can become unusable. For example, a common error is related to the Callfile – a table used to store call session information when a session is generated. If this table is damaged, you will receive an error when attempting to generate a call session. Clearly, corruption like this can be quite an inconvenience, and should be avoided if possible.
So what can you do to avoid corruption in your ReminderPro database – or at least be able to recover quickly if it does happen?
Let the call session finish if you can.There are times that it can seem ReminderPro is taking a while to wrap up a call session. If possible, let it end by itself. Using an alternative means of ending the session is a primary cause of data corruption.
End the call session through ReminderPro if you must. If you must abort a call session, try to do it through ReminderPro. Click the Stop button and/or Manual Finish button to end it, and let it finish doing it’s thing. Avoid “ending task” on ReminderPro – or using other alternative means to force it to stop – if you can.
Backup the ReminderPro directory. While nightly backups are not necessary for ReminderPro, we do recommend taking a one-time backup of the entire ReminderPro directory. This is not only useful in case of data corruption, but also provides assurance that you have copies of your recorded messages somewhere.
Data corruption cannot always be avoided, and it doesn’t happen very often. These ideas should help minimize the instances of it.