Frequently Asked Questions:
Which version should I use, 32bit or 64bit?
32bit programs need to use the 32bit Oracle Client. 64bit programs need to use the 64bit Oracle Client. Use the version that matches the Oracle Client that you have installed. The 64bit version can access more memory than the 32bit version, but beyond that there are no differences.
What Oracle Client versions are supported?
It's important to use the version that works with your Oracle Server. In general this means that you should use an Oracle Client version that is equal to or higher than the highest Oracle Server version that you use. Newer versions of our products use the Oracle Unicode Client calls by default and so require clients that support these calls. If you need to use an older Oracle Client you can uncheck the "Use Uncode Oracle Client Calls" option on the login options window. In general we recommend the 11.2 Oracle Client or higher as Oracle fixed a problem described in the next question.
Why am I getting error ORA-12154 when I try to login to Oracle on my 64bit Windows Operating System?
On 64bit Operating Systems the installer will install 32bit software into a directly containing "(x86)". Some versions of the Oracle Client won't work if an application using the client is installed in a directory path containing "()" characters. To fix this just install the program to a directory that doesn't have "()" characters in it or install a newer version of the Oracle Client that doesn't have this problem. This is Oracle Bug #3807408 and should be fixed in newer client versions (note: seems to be fixed in the 11.2 client.)
Why am I getting an error "Can not initialize OCI" or "Cannot load OCI DLL" when I try to login?
This means that the program couldn't load the Oracle Client. This can happen in the following cases:

a. The Oracle Client is missing or installed incorrectly.
b. You are trying to use the 64bit version of the Oracle Client with either Golden 5.x or the 32bit version of Golden 6.x. Golden 5.x needs the 32bit Oracle Client.
c. You are trying to use the 32bit version of the Oracle Client with the 64bit version of Golden 6.x. Golden 6.x 64bit needs the 64bit Oracle Client.
d. The user does not have read or execute rights to the Oracle Client files.

To quickly check if it's a rights problem, right click the startup icon and choose "Run as administrator". If that fixes the problem then the issue is that the user account is missing read or execute rights to an Oracle Client file.
Why am I seeing #data_error# messages in the datagrid or the results look like Chinese characters?
This generally means that the Oracle Client version is older than the Oracle Server version or doesn't properly support Unicode. Either install a newer Oracle Client or uncheck the Unicode OCI Calls option in the login options window. Note that using an Oracle Client version older than your server can cause problems with certain newer datatypes like timestamps.
I'm using 64bit Windows and have the 64bit Oracle Client installed. How should I also install the 32bit Client so that it can be used by Golden 5.x and it won't affect my existing programs? (Note that Golden 6.x has both 32bit and 64bit versions available.)
The best thing to do is to install the 32bit Oracle Instant Client to a directory and set the "Oracle Client DLL" field in our program's login options window to the oci.dll file that is in the Instant Client directory. If you do this then there is no need to change the system path. You can use the TNS_ADMIN environment or registry setting to force the location of your tnsnames.ora file.

a. Install the 32bit Oracle Instant Client. You can use the Instant Client Package - Basic Lite files (depending on what features you need.) You do not have to put the instant client directory in the system path.

b. Install Golden and go to the Login Options window (options button on the login window) and set the "Oracle Client DLL" field to the OCI.DLL file from step a.

c. You can then either use the EZConnect method for the login database field (e.g. //hostname/sid) or use a tnsnames.ora file. You can use a tns_admin environment or registry variable to force the location of the tnsnames.ora file if needed.
I need more help, what's the best way to get it?
Email your issue to We'll take a look and get back to you ASAP. Please describe the problem and if possible include your connection diagnostics (see the next question.)
How do I send you the Connection Diagnostics?
First attempt to login. Click 'Ok' on any errors and then click 'Close' on the login window. Now choose "Connection Diagnostics" from the help menu. There's a button to copy the text to the clipboard so you can easily paste it into an email message. Send it to us ( with a description of the problem and any error messages and we'll get back to you ASAP.