Running two separate Chintaro databases concurrently (Access only)

Modified on Tue, 17 May 2022 at 11:29 AM

Some organisations choose to run 2 completely separate Chintaro databases concurrently. An examples of this is when an organisation has highly confidential Clients in one database which very few staff have access to, but another database for their other Programs which many more staff can access. Organisations who choose to run 2 completely separate databases treat them as completely independent organisations where the databases do not share information and data is never transferred. 

This solution details how to run 2 independent Chintaro databases concurrently.


If you already have 1 existing Chintaro Database installed and you will be installing the 2nd database in a Shared Drive

Search for the location you will be installing the new databases by right clicking your existing Chintaro icon and selecting Properties. 

In the Target Line, you will see /wrkgrp and immediately after this is the location of the current Chintaro databases (EG S:\Chintaro\Data):

Navigate to the Shared Drive in the Target Line.

Installing the Data databases

Add a new folder in your shared drive and name it something other than CHINTARO, for example, CHINTARO_PROGRAM NAME (i.e CHINTARO_CRISIS).

The databases will be sent to you in a Dropbox link. If you have received the entire Data folder as a zipped file, unzip it and copy it in to your new Chintaro folder. 

If you have been sent databases not in the entire Data folder, create a new folder within the CHINTARO_PROGRAM NAME folder called Data

Copy the 4 database files from Chintaro Support to the Data folder (this will be provided to you in a Dropbox link). You will need to create another 5 folders within the Data folder also, as follows:

Copy the 4 database files (rhmdat.mdb, rhmref.mdb, rhmaud.mdb and rhp.mdw) to the Data Folder. The databases are now installed.

Installing the Code database (Chintaro Client)

Create a new folder in the C Drive of the users PC called CHINTARO_PROGRAM NAME. Download the latest version of Chintaro from this link and paste it in the new C:\CHINTARO PROGRAM NAME folder. Download the file from the bottom of this solution and copy the 2 files to the C:\CHINTARO_PROGRAM NAME folder. 

This zip file contains 2 files - a Chintaro Icon and a Chintaro Shortcut.

Creating a Shortcut for the users to launch the new Chintaro database

Copy the shortcut from the C Drive and paste it on the desktop of the PC of any Chintaro user. Change the name of this icon to reflect the new database name (EG CHINTARO - PROGRAM NAME):

Right click the new icon, and select Properties. In the Target Line, change the location to be:

"C:\Program Files (x86)\Microsoft Office\root\Office16\MSACCESS.EXE" "C:\CHINTARO_PROGRAM NAME\chintaro.mdb" /wrkgrp "\\SERVER:\CHINTARO_PROGRAM NAME\data\rhp.mdw"


*Location of MSAccess may differ to example.

*Where the code database is installed (C:\), replace PROGRAM NAME with the actual location of the code database (chintaro.mdb)

*Where the data databases are installed (\\SERVER), replace \\SERVER:\CHINTARO_PROGRAM NAME\ with the actual location of the databases (rhp.mdw).

Launching your new Chintaro Database

Double click on your new Chintaro icon (CHINTARO_PROGRAM NAME).

In the log on box, enter the username sa and password sa

Change the bulletin board to notify users that this is a new database. NOTE: This step is very important. Click System Maintenance > Bulletin Update. Change the text in the Bulletin Update to reflect nice and clearly that this is a separate Chintaro database, for example:

Click Update. Users will now be able to differentiate between their 2 separate databases.

If you require further assistance from Chintaro Support

Please raise a ticket with Chintaro Support by emailing if you would like further assistance.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article