There are a few different ways that your Chintaro database can become corrupted.


The Database becomes too large 

If you have not run a repair and compact for a while, your database may become too large, and corrupt. It is always recommended that you run a repair and compact at least weekly to prevent corruptions, and to improve the speed and performance of Chintaro. Instructions on how to set up a Chintaro Repair and Compact are found here.



Environmental Network Problems

If you have a poor connection to your network, Chintaro may crash and your database can become corrupted. Chintaro requires a constant connection to the network, and if this is broken (even for a nanosecond) it can cause Chintaro to become corrupted. 


If you are experiencing frequent corruptions, we suggest you get in touch with Chintaro Support to discuss moving your databases to Chintaro Cloud, where Chintaro will host your databases on an Amazon Web Server. 


Leaving your Chintaro session open overnight

One way that a database can become corrupt is when users leave their Chintaro session open overnight. At some stage overnight, your network might drop its connection. This is the most common cause of a corrupt database.

It is always recommended that all users completely log off Chintaro each night.


Leaving your Chintaro session open can also be a breach of security. An open session leaves your session exposed to anyone coming in and changing the data. 


Exiting Chintaro Incorrectly

Corrupt databases can occur when users incorrectly exit Chintaro incorrectly, by clicking the X at the top right of the screen to close the session. 

blob1476420166988.png


It is always recommended that users exit Chintaro in one of 2 ways:


1. Click Quit to Windows on the Main Menu

blob1476420228925.png



2. Click Exit on the Home Screen

blob1476420255207.png


How do I prevent a database corruption?


To prevent database corruptions, all users should:

1. Close their Chintaro session when they have finished using the system

2. Exit Chintaro correctly using one of the 2 ways described above 

3. Run regular repair and compacts (at least weekly)


To further prevent database corruptions, it is recommended that your System Administrator regularly runs a Repair and Compact of the rhmdat.mdb file. 


Instructions on how to set up a Chintaro Repair and Compact are found here.