The likeliest reason is that the new client is not pointed properly. Perhaps you mapped a drive or used UNC, neither of which works with Gradience. Perhaps a character is missing. In any event, the first thing to try is to replace the ini file that the new client is using.
The name of this file is Hrware.ini. It is located at C:\ProgramData\Gradience. By the way, the ProgramData folder is often hidden on new computers so you may have to unhide it. If you are unsure how to do this go online for the steps to do so for your particular operating system.
How to Replace it:
If you have another client workstation that [can] connect to the data go to that computer and copy it's hrware.ini file and use that to replace the one on the new, non-working client workstation.
If you don't have another working client you can go to the machine where the database resides to copy the hrware.ini file. If you do this though, you will have to alter the [copied] file before using it to replace the bad one on the new, non-working machine. The image below shows what must be changed. Change the word Localhost to the name or the IP address of the computer/server that is hosting the data. Leave the PATH line alone! The drive letter indicated on the PATH line refers to the host machine, [not] the client.
Save what you've done and try to launch Gradience on the new client once again.
Make sure that you are using the same iterations of the software on ALL your machines. 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 high chances of unsolvable data corruptions.
If the software still won't run visit this ARTICLE.