Through the GM.ini, the GoldMine Administrator, can set a global setting presence for your GoldMine.

For example, to disable all users access to the GoldMine taskbar the GM.ini would read as follows:

[GoldMine]
[User-OverRide:gmbar]
show_gmbar=0

This next one sets the GoldMine default tabs that are to be displayed for all users. You are defining a
global setting for the default GoldMine tabs, overriding any user selected tab order.

[User-OverRide:GoldMine]
RoTabItems1 = 1;2;4;5;6;7;8;9;10;11;12;13;14;

These overrides are a great way for the GoldMine Administrator to enforce company wide standards for their GoldMine.

NOTE: Any override settings configured by the Administrator in the GM.ini will ALWAYS override a user’s settings, even if they attempt to change their local preferences – GoldMine will never apply the username.ini settings if a corresponding user-override exists in the GM.ini.

You can add the following string to each USERNAME.ini file and it will override the default tab names on a user by user basis:

ROTabs1=Summary,Fields,INTRANET,Notes,Contacts,Details,Referrals,Pending,History,Links,Members,Tracks,Opptys,Projects,Tickets,Events,Licenses,Products,Renewal,Sales,Sent

Or, alternatively, you can change every users tab names by adding the following to the GM.ini file:

[User-OverRide:GoldMine]
ROTabs1=Summary,Fields,INTRANET,Notes,Contacts,Details,Referrals,Pending,History,Links,Members,Tracks,Opptys,Projects,Tickets,Events,Licenses,Products,Renewal,Sales,Sent

As you can see, you need to just change the tab name to the required text. Simple as that!

NOTE:  Adding the ROTabs1 field to the .ini file won’t affect the ROTabItems1 values. The ROTabItems1 option holds the order in which each users tabs are displayed – and fickle users will get angry if you change it! All we are doing here is changing the default name mappings, NOT the order of the tabs.

Another GoldMine installation is running.

What you need to do is:

Run regedit (Start> Run> regedit).

Go to HKEY_LOCAL_MACHINE >> SOFTWARE >> FRONTRANGE SOLUTIONS.
Delete the folder GMinProgress.
Exit regedit.

Retry the installation.

Note: If you can’t find the FRONTRANGE SOLUTIONS Registry Key, search for it by clicking on Edit >> Find, in the Registry Editor.

”HTML_CAL_Notes=0”

NOTE: The GM.ini file can be found in your GoldMine Directory, ie;  G:\GoldMine or C:\Program Files\GoldMine

If you are not sure of your path, in GoldMine go to Help >> About GoldMine >> and then click on System.  The System Files path will tell you the root directory for GoldMine.

In GoldMine Premium there is a ‘Recently Viewed’ contacts window that will display the last 20 or so contacts that you visited. You can change the number of recently viewed contacts that are displayed.

When you perform a database rebuild (and a few other functions), the BDE asks windows how much free disk space there is (in an attempt to avoid shredding your database.) This would be a good idea except the BDE trips up if the amount of free space you actually have (in GB) is evenly divisible by 4. So machines with 4.3GB, 16.8GB, 24.5GB, 88.2GB, etc. all choke on the regular BDE free-space request and report that there isn’t enough free space available.

When you NEED to perform a database rebuild, this can be a real problem. In the past, the solution was to free up (or take up) disk space to a point where the free space was not divisible by 4. This could get tricky, however, given that your database files shrink a bit when they’re packed and rebuilt by the maintenance procedure. This sometimes left GoldMine administrators doing a delicate dance with their database and free space throughout the maintenance procedure. Hair-raising, to say the least.

The fix (available via download below) basically routes just this BDE request (the one that checks your free disk space) to a hacked DLL that you must place in your \windows\system32 directory which properly reports the value.

Numerous GoldMine admins have reported success with it.

Cause: GoldMine license file has been renamed.

Reason: Administrator may have reason for not allowing users to login. If you are the administrator and your system suddenly went into this mode, it means that your database maintenance crashed in the middle of the operation. You will need to follow the following steps to correct the problem.

1. Ensure that all GM files are closed (shut down OmniRush DBIO, GoldSync, etc.)
2. Browse to the root goldmine directory and find the file named license.dbx or license.dbu
3. Rename this file to license.dbf
4. Backup your goldmine directory to a backup location. (copy it)
5. Login to GoldMine as a MASTER user.
6. Perform a database maintenance

If your system crashes again, you may have low disk space or a serious database corruption which can’t be fixed with maintenance. Free up disk space or contact First Direct Corp for further assistance.

After the error, GoldMine does not start.

What’s going on is that every GoldMine version has a digital signature and the one used with GoldMine 8.0.x expired in early December, 2009. That means that the windows User Account Control (UAC) feature will not allow it to run.

UAC is a feature that is built into Windows Vista, Server 2008 and Windows 7. You know it as that annoying feature that produces a constant stream of messages along the lines of, “Hey, it looks like you are trying to double-click an icon. Did you know that icons could run terrible viruses? Please click OK to confirm you want to run the thing you double-clicked!”

 A lot of people have simply turned UAC off, but those who have not are now finding themselves unable to run GoldMine. There are two possible solutions 1.Turn off UAC like the rest of us. Of course, if you haven’t done that by now, you probably have a very good reason (like you use Quickbooks, which requires it) or you enjoy the implied additional security features. 2.Patch to version 8.5.x of GoldMine (free to customers current on their Frontrange Maintenance) and enjoy the many fixes and new features introduced therein (including a new digital certificate.)

Nothing’s wrong with your GoldMine, really. What it’s saying is that the list of items you’re looking at (the History Tab , for instance) has more items with notes than can be handled by your Borland Database Engine’s setting for the number of notes fields to cache in memory.  This doesn’t mean the program or database has a problem, it just means that with your current BDE settings, you’re trying to work with too much data at one time.

If you continue to receive this error on even relatively short lists of information, you may need to increase the number of BLOBs that are cached in memory at any given time. To change this setting, open the BDE Administrator from the GoldMine tools menu (or the Windows Control Panel) and locate the proper database alias*.  Highlight it and note the BLOBS TO CACHE setting on the right side. Adjust it, as necessary. The higher the number you set, the more items you can work with in places like the activity list. Keep in mind, however, that the higher the number, the worse your performance could be. A happy medium is typically anywhere from 512 to 1024.

*If you’re not sure of your database alias, you can check it under Help|About|System in GoldMine. It will be listed for the GoldMine Files item. Your alias may look something like this: MSSQL: GoldMine_Data: dbo. The important part in this example is GoldMine_Data.

If you need further assistance contact First Direct Corp directly.