Updating Chintaro Access Instructions

Modified on Fri, 07 Jul 2023 at 02:00 PM

NOTE: IF YOU ARE A CLOUD USER YOU DO NOT NEED TO UPDATE, CHINTARO SUPPORT DO THIS FOR YOU.


Download the latest Chintaro version from this link:  Chintaro 2023.07.06 (6 July 2023). The link will open up to our Dropbox account on your web browser. Click Download to start downloading the file.


These instructions are for updating Chintaro if you are an Access user. If you are unsure which version of Chintaro you are running and whether you need to update, please log into Chintaro and see this solution: Which version of Chintaro is my Organisation currently running?

NOTE: Before you begin the update, make sure all users are completely logged out of the system.  If there is anyone else logged in, the update will not work, and you will get error messages after you have updated. 


TABLE OF CONTENTS


STEP 1: Log Out

Ask all users to log out and check that they have done so. You can check to see if all users have logged out by using this solution: System Maintenance - Current Users


STEP 2: Download Latest Version

You will need to download the latest Chintaro version from the top of this solution. The link will open up to our Dropbox account on your web browser. Click Download to start downloading the file.


The file you just downloaded is a zip file containing a file called chintaro.mdb. The Chintaro client (chintaro.mdb) will usually be installed on the local drive (usually C:\) of each PC that will be used to run Chintaro. This version is suitable for 32 bit or 64 bit Access databases users.



STEP 3: Copy File to Chintaro Folder

Once you have downloaded chintaro.mdb from the website, copy this file (chintaro.mdb) to the location of your existing version. This is often C:\Chintaro but may not be. You can check the location by looking at the properties of the shortcut you usually use to launch Chintaro. The location of the Client file in this example is “C:\CHINTARO\chintaro.mdb”.




If you are using a remote desktop environment, it is important that each user has their own instance of chintaro.mdb running. Usually, this is installed under the \Users\Folder structure, making use of the Username% parameter.


STEP 4: Launch New Version

Launching the new version of Chintaro. Log in to Chintaro by double-clicking the shortcut file using your normal login details. You will see the following login dialogue box:


The first time you log into the new version of Chintaro, there will be a noticeable delay before the system starts. This is due to Chintaro making changes to the database, and shouldn’t take more than a few extra seconds. If this takes a long time, it will be due to another user being logged in. If you can get them to log out, it will speed up the process.


Once the system opens, check that Chintaro has updated to the latest version (under the Logo on the home page).



STEP 5: Log Out

Once you have confirmed that the update has applied correctly, log out of Chintaro so that you can update the other users.


STEP 6: Copy File to Data Folder

Copy your copy of chintaro.mdb from your C:\Chintaro folder and paste it in your Chintaro\Data folder. This folder is often on a shared network drive but may not be. If you are unsure where your Chintaro\Data folder is, please see this solution for instructions on how to find out: How to find the location of your Data Folder



STEP 7: Copy File from Data Folder to All Chintaro Folders

Copy the chintaro.mdb file from the Chintaro\Data folder around to all other user’s PCs. 



STEP 8: Sign In

Advise users that they can log in.


If you require further assistance from Chintaro Support

Please raise a ticket with Chintaro Support by emailing support@chintaro.com.au 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