--IMPORTANT!-- The server must be the first thing to be updated. Once the server is updated, the clients can follow.
These instructions are for those who are switching from running Gradience on a single computer to running it on multiple computers where the original standalone computer will play the role of server as it continues to host the data that it will now share-out to other computers where Gradience will be installed.
If you prefer to literally move the software and the data to an actual server causing the original computer to become a client and perhaps add more clients, these are the wrong instructions. You need to click HERE.
Please print this before proceeding further!
When you click to download the installation file, you will be taken away from these instructions. You'll need the print-out to know what steps to follow.
This process involves installation. Before proceeding, please read the warning below.
--CAUTION!-- Please be sure that you are running the same [iteration] of the same [version] on each computer where the software is to be installed including the server if you wish to install it there.
When you run different releases of [any] version on various machines that are all pointed to the same database, you will encounter strange errors with chances of unsolvable data corruption.
Download the installer to our latest version here.
At the Original Computer:
1. Go to C:\ProgramData\Gradience and copy the Hrware.ini file and save it in a neutral location.
2. Open the copied ini file in the neutral location and look at the line very near the top that begins with...
3. Change the word Localhost to the name of the original computer or it's IP address.
4. Save the change and close the file.
At Each New Client:
1. Go to C:\ProgramData and create a folder there named Gradience.
2. Go to where you saved the [altered copy] of the Hrware.ini file and copy it again..
3. Go to C:\ProgramData\Gradience and paste the copied ini file. This will pre-point the software.
4. Install the appropriate version.
Click here to troubleshoot connection issues.
--TIP!-- I highly recommend that you automate Gradience backups for the end-users. Even if the server does nightly backups, it's just way faster and simpler to restore a Gradience backup than to recover a copy of the database captured by your nightly server backups. The links below cover this.
To back up your data automatically visit this ARTICLE
To restore data that was previously backed up visit this ARTICLE