Castell Computers

Have you ever tried to Google some odd error message you got from GoldMine? Have you found way too many irrelevant references to movies and such?

Google now provides a way to create your own focused, community driven search engine for a specific subject area. I took the liberty of creating a GoldMine one. It can be found here: Google for GoldMine Tech Stuff

Much like the search wiki mentioned in an older post, this search engine can be customized by the users! If you see something in your results that has nothing to do with CRM software or GoldMine, tell the engine and it will respect that the next time you (or anyone else) searches for the same thing!

The search box can even be embedded on other web sites or e-mails, even! Here’s a simple version you can try out right here:

What may be the FINAL GoldMine 6.7 update patch was released yesterday. This is the first GoldMine 6.x patch in about two years.

Castell Computers is not currently recommending that users install this patch as there are a number of known bugs in it. FrontRange is working on yet another 6.7 patch, to be announced.

Fixes include:

1. New: GoldMine 6.7 is now compatible with Microsoft Internet Explorer 7.
2. New: The GoldMine link for Microsoft Word has been updated to version 6.7.216. No details on what, exactly, is fixed in it.
3. New: GoldSync now can support All User synchronization, bypassing the selected Users’ calendar. This applies only to Microsoft SQL Server databases.
   Requires the following GoldSync.INI setting:
   [GoldSync]
   AllUsersForFilteredRecs=1 (default is 0 – off)
4. Fixed: Issue where existing database tables could be deleted if database connectivity was lost after logging in.
5. Fixed: SQL queries have been optimized to minimize issues where blocking could occur by relinking, deleting, or sending an e-mail, completing a multiple user activity, or synchronizing with a Palm device.
6. Fixed: Issue where online help was not displayed on workstations.
7. Fixed: Issue where tagging a record and then printing a report caused all records in the Contact Search Center to become tagged.
8. Fixed: Issue where outgoing e-mail messages were inaccessible after the contact record is deleted. E-mail messages now are retained when a contact is deleted.
9. Fixed: Issue where deactivating the GoldMine E-Mail option did not disable adding GoldMine E-mail accounts to distribution lists.
10. Fixed: Issue where a deletion filter was ignored when a non-master user synchronized and record curtaining was in use.
11. Fixed: Issue in which right-clicking to complete a recurring multi-user activity followed closely by a recurring single-user activity may result in the improper completion of all activities.
12. Fixed: Slow calendar display response with Events.
13. Fixed: XML validation error when importing special characters.
14. Fixed: iCalendar import issue where updating exceptions on a recurring activity series would fail.
15. Fixed: Incorrect date assigned to imported calendar and history items.

In the mean time, there are some interesting things to note about this update:

1. You DO NOT need to have current UPP to update to this version. You only need to be on an older version of 6.7 already.
2. This update will synchronize with earlier version(s) of 6.7 without missing a beat. Of course, it’s always a good idea to be on the exact SAME version on all remotes and servers.
3. The release notes, EULA and Firebird client (for E licenses) are placed in c:\program files\goldmine\, regardless of your installation choices.

Guess it’s time to take a look at IE7?

The long-awaited patch for GoldMine 7 (version 7.0.61201 (aka 7.0.4)) is now available via Net-Update to customers with a current maintenance contract.

A lot of work has gone into this release and a lot of problems with GoldMine 7 are, hopefully, a thing of the past.

“But Doug, what’s been fixed?!”

I’m glad you asked. The following long list comes directly from the included release notes:

1. E-mail address field is not imported during XML import
2. After removing fields tab from view, fields still appear on another tab
3. HTML toolbar doesn’t appear after switching e-mail templates
4. New user setting is needed to enable user without contact record deletion permission to delete unlinked GoldMine E-mail.
5. Change in Forecasted Sale ‘Price’ field in recurring forecasted sale does not update Opportunity Manager ‘Revenue’ field
6. ODBC source for Crystal Reports may appear correct, but settings are not being read when connecting to ODBC
7. Completed activity may not synchronize to Outlook when contacts are omitted from Outlook sync
8. Unable to type in HTML notes field of activity if cursor is on space used by HTML toolbar
9. Scheduling conflict warning only warns of conflict for one user even if there are multiple conflicts and does not warn of resource scheduling conflicts
10. Database Alias Manager should have a browse button for Firebird database location
11. Email rules do not recognize any characters after @
12. Upgrade process automatically upgrades contact set in Common folder
13. Web Import does not populate curtaining level in STATUS field
14. GoldMine iCalendar is off by one hour from Outlook using day-light savings time in Australia
15. Forced log out does not work for specified time
16. Automatic Maintenance does not execute
17. E-mail merge does not support certain HTML graphics that can be added when building a template
18. Key values are defaulting to the first value in the F2 lookup rather then the value that was selected during record creation, when using rule based record types creation
19. Cannot login after deleting all aliases in Database Connections Manager
20. “Invalid retrieval contact set path” error in process monitor logs when syncing multiple contact sets
21. Forwarded plain/text email shows HTML tags of signature file
22. When fast filing e-mail messages under the Pending tab, you can only do 2-3 messages before the Fast Filing button stops working
23. Cal items fail to sync using Send Contact Related Options for “All filtered records and user-scheduled activity records” outside of filter
24. Records types on Server installation do not sync to remote after one button install
25. Cannot create new database using “Copy the data from the current files to the new database” with large database
26. GoldMine will not exit when opportunity manager window has focus and a Server Agent is running in the background
27. Error when doing “save as” new field in contact record with large database
28. API issue: When 4-th parameter (owner) to DDE function LinkDoc is not specified, it submits empty user name, not currently logged in user
29. When importing a DBF file with date fields, the import stops after first record
30. Synchronization can result in orphaned data when deleting history items
31. Installer cannot upgrade from dBASE to MSSQL
32. Error window appears when changing install path in one-button installation
33. Only one alias is transferred to remote using one-button installation
34. Switching between contact sets prevents GoldSync processes from being restarted
35. Error when selecting “Close All” without stopping all processes
36. Licensing error after installing O-license and GISMO
37. Installer errors if .NET framework is not present during Management Intelligence install
38. Quoted text appears twice within the message body when assigned ‘reply’ template uses inserted file
39. E-mail address can get linked incorrectly after editing a pending activity from the activity list and clicking on an empty email address field
40. After deleting contact record, e-mails associated with that record can no longer be opened.
41. Records do not sync if the corresponding TLogs have been purged
42. Activity scheduling is slow when using Firebird
43. Merging records causes orphaned e-mail messages
44. Microsoft Word does not warn about unsaved data after installing GoldMine Plus for Microsoft Word
45. Records retrieved from remote site sync back at next session
46. Cannot correctly add E license number through “Add Other License” button in GoldSync Site Group Wizard
47. Syncing only linked e-mail attachments causes “Cal/History record is missing or corrupt” error message
48. Some licenses are generated with O (letter ‘O’) and 0 (digit ‘0’) together
49. Text Search does not return correct results
50. Cannot add a group of contacts into distribution list via CSC action button
51. Softphone does not work from a network shortcut
52. User is not able to add GM+View
53. Softphone does not auto answer when used with GMIPVS
54. When converting an additional contact to a new record, AP does not get attached
55. Completing an Opportunity will lose original Price and Forecast data.
56. Office Link breaks automated process due to Save As window
57. Incompatible license found when upgrading an Undocked license running on MSDE
58. Unchecking Rich Text option does not change the HTML body of an email to Plain Text
59. When the cursor is highlighted on a completed sale in the history tab, completed calendar items show same currency amount
60. Import from SQL table tool does not support all non-GoldMine tables.
61. Error when completing activity after closing Contact Window
62. No warning when overwriting backup file
63. Reset of Palm after initial sync causes GoldMine data to be deleted
64. Prompt to use wizard or manual method for new opportunities can only be disabled for current user session
65. Unverifiable digital signature causes body not to be available
66. Changing CC recipients to TO recipients on an email causes primary recipient to be changed to group (all).
67. Clicking ‘Edit’ button in Distribution List Center brings inappropriate ‘Contact Search Center’ dialog box
68. Error when changing the name of the current DB alias
69. Calendar/opportunity items are omitted from one-button install when contact database and GMBase are in different locations
70. Resizing Calendar dialog box loses the time lines of the main pane
71. Resizing Calendar dialog box can cause the ‘Task’ pane to disappear
72. Contact data truncated from XML import
73. Can’t finish installation when installing Firebird Client instead of server
74. Auto Update Statistics and Auto Create Statistics not turned on by installer
75. API issue: WriteGMUser call exits with error code 0
76. Export to XML or DBF ignores filters
77. Transfer set only includes contacts from the first contact set
78. ReadMail API function returns incorrect Body Value
79. Mailmerge to contacts with German characters in the contact name produces incorrect characters in the Contact name
80. History tab displays oldest items first
81. Secondary contact search only works for master users

See any of your pet peeves? Maybe it’s time to upgrade!

If you get a message that “This Contact set is only accessible to the Goldmine System with Serial Number…..” upon attempting to open a contact file, you can feel helpless and alone. You might begin to ask yourself questions like:

Why has this happened to me?

What can I do to fix it?

What IS that smell?

This problem occurs when you attempt to open a GoldMine contact set that has been locked down by an innocuous little check box. To see this seemingly harmless check box, go to File|Open Database and hit the Properties button.

It says “Grant access from this GoldMine License only.” Sounds like a good idea, huh? Maybe, but if you choose to check it, you will need to remember it the next time you make changes to your installation (or attempt to recover your backup!)

So, let’s say you’ve got a handy backup of your GoldMine contact files, but you don’t happen to have the entire GoldMine folder (complete with the license file). It’s not an uncommon scenario. You install GoldMine from the CD, enter one of your many licenses and drop in your database files. You then encounter the message:

This Contact set is only accessible to the Goldmine System with Serial Number 12345678

Panic may set in, you might even consider taking it out on the monitor with the nearest paperweight.

As Jeff Spicoli said, “Relax, alright? My old man is a television repairman, he’s got this ultimate set of tools. I can fix it.”

All you need is BR7 or SQL Query analyzer (depending on whether your dBase or SQL-based.) Locate the record in the CONTSUPP table/database file with an accountno containing “SYSTEM-REC”. An SQL query, much like this one:

select * from contsupp where accountno like '%SYSTEM-REC%'

…can help you find it. Once you locate this record, delete it and you will find that the lockdown is lifted and your data is accessible.

…and your brother is not going to kill us — or anything else…

GoldMine has a lot of built-in warnings that will pop up on you when you do various things in the program. They can be informative and helpful but they can also be down right annoying. Here’s how to turn them ALL off.

WARNING: Turning off the warning messages may result in you accidentally doing something dangerous to your data without getting a ‘WARNING! You’re about to do something dangerous, are you sure?’ prompt. Proceed with caution!

DISCLAIMER: Castell Computers cannot be held responsible for anything that happens to you, your database or career as a result of turning off the warning messages in your GoldMine.

Now that we have that out of the way… Locate your USERNAME.INI in the GoldMine directory and add (or replace) the following section:

[Warning]
InetWarnAboutDelete1=0
InetWarnAboutRTF=0
ORGCHARTDRAGWARN=0
WarnAboutHtmlFRAMESinIE=0
BrowseSort=0
WarnChangeMasterPwd=0
WarnMakeBackup=0
WarnCMSalesForecast=0
NotesLimit=0
WelcomeAutomatedProcesses=0
WarnAboutGlobalReplace=0
WarnAboutFBRange=0
WelcomeGoldSync=0
WarnCMTemplatesEmail=0
WelcomeRecTypes=0
INETWARNABOUTCOMPLETE=0
WarnAboutDeleteRecords=0
WarnAboutImport=0
WelcomeInfoCenter=0
WarnAboutCopyMoveRecords=0
WarnAboutPalmDesktop=0
WarnAboutSCSpeed=0
WarnAboutMergePurge=0
WelcomeCampaignManagementCenter=0
WelcomeDistList=0
WelcomeInetEmailRules=0
WarnAboutACTOutlook=0
WarnAboutExcel=0
InfoWarnAboutDrag=0
WarnCMTemplatesWrite=0

Note that these warnings cover GoldMine 6.7. some of them don’t apply to older versions (though it doesn’t hurt to have them in the INI file) and there are others that apply to GoldMine 7.0 that aren’t included here.

Also, feel free to change values you prefer to keep getting warned about to 1 instead of 0!

A client sent in a question today and I may have gotten a little carried away with the answer. Maybe the information will prove useful for others!

Question 1:
Is it possible to setup a special rule where certain records can pull up different Field views (from the fields screen designer we can setup different views). For example, I had mentioned before we might be using the Merge field to contain a specific record type. Depending on that record type it would pull up a different field view.

Answer:
It IS possible, but the feature doesn’t work well. It can be found under File|Configure|Record Types Administration Center. There you define rules and record types and different field layouts, coloration, etc. In reality, however, it’s just plain buggy. I would stay away from it until version 7.0.4 (which supposedly should provide much-needed stability to this feature.)

Until then, however, you CAN change field colors and such based on rules by placing expressions in the color tab of the fields’ properties. Both the label and data colors can be customized.

iif(left(Contact1->Key3,1)="A", 32768, iif(left(Contact1->Key3,1)="B", 16776960, iif(left(Contact1->Key3,1)="C", 3145645, iif(left(Contact1->Key3,1)="D", 42495, iif(left(Contact1->Key3,1)="F", 255, 0)))))

That’s an extreme example of a coloration expression I use in my own GoldMine. It causes the label of my ‘Rating’ field (key3) to be one of five colors depending on the contents of the field being A, B, C, D or F.

Similarly, I have a field that shows me how much time a given contact record has remaining with me. If the number is positive, the field is green, if the number is negative (or zero) the number is red. It’s a much simpler expression:

iif(contact2->utimeleft<=0,255,32768)

The numbers represent colors. I have a a pretty long list of color codes listed below (I’m not sure who posted it in the FrontRange forum, but I socked it away for future reference months ago):
————————————————–
AliceBlue 16775408
AntiqueWhite 14150650
Aqua 16776960
Aquamarine 13959039
Azure 16777200
Beige 14480885
Bisque 12903679
Black 0
BlanchedAlmond 13495295
Blue 16711680
BlueViolet 14822282
Brown 2763429
BurlyWood 8894686
CadetBlue 10526303
Chartreuse 65407
Chocolate 1993170
Coral 5275647
CornflowerBlue 15570276
Cornsilk 14481663
Crimson 3937500
Cyan 16776960
DarkBlue 9109504
DarkCyan 9145088
DarkGoldenrod 755384
DarkGray 11119017
DarkGreen 25600
DarkKhaki 7059389
DarkMagenta 9109643
DarkOliveGreen 3107669
DarkOrange 36095
DarkOrchid 13382297
DarkRed 139
DarkSalmon 8034025
DarkSeaGreen 9419919
DarkSlateBlue 9125192
DarkSlateGray 5197615
DarkTurquoise 13749760
DarkViolet 13828244
DeepPink 9639167
DeepSkyBlue 16760576
DimGray 6908265
DodgerBlue 16748574
FireBrick 2237106
FloralWhite 15792895
ForestGreen 2263842
Fuchsia 16711935
Gainsboro 14474460
GhostWhite 16775416
Gold 55295
Goldenrod 2139610
Gray 8421504
Green 32768
GreenYellow 3145645
Honeydew 15794160
HotPink 11823615
IndianRed 6053069
Indigo 8519755
Ivory 15794175
Khaki 9234160
Lavender 16443110
LavenderBlush 16118015
LawnGreen 64636
LemonChiffon 13499135
LightBlue 15128749
LightCoral 8421616
LightCyan 16777184
LightGoldenrodYellow 13826810
LightGreen 9498256
LightGrey 13882323
LightPink 12695295
LightSalmon 8036607
LightSeaGreen 11186720
LightSkyBlue 16436871
LightSlateGray 10061943
LightSteelBlue 14599344
LightYellow 14745599
Lime 65280
LimeGreen 3329330
Linen 15134970
Magenta 16711935
Maroon 128
MediumAquamarine 11193702
MediumBlue 13434880
MediumOrchid 13850042
MediumPurple 14381203
MediumSeaGreen 7451452
MediumSlateBlue 15624315
MediumSpringGreen 10156544
MediumTurquoise 13422920
MediumVioletRed 8721863
MidnightBlue 7346457
MintCream 16449525
MistyRose 14804223
Moccasin 11920639
NavajoWhite 11394815
Navy 8388608
OldLace 15136253
Olive 32896
OliveDrab 2330219
Orange 42495
OrangeRed 17919
Orchid 14053594
PaleGoldenrod 11200750
PaleGreen 10025880
PaleTurquoise 15658671
PaleVioletRed 9662683
PapayaWhip 14020607
PeachPuff 12180223
Peru 4163021
Pink 13353215
Plum 14524637
PowderBlue 15130800
Purple 8388736
Red 255
RosyBrown 9408444
RoyalBlue 14772545
SaddleBrown 1262987
Salmon 7504122
SandyBrown 6333684
SeaGreen 5737262
Seashell 15660543
Sienna 2970272
Silver 12632256
SkyBlue 15453831
SlateBlue 13458026
SlateGray 9470064
Snow 16448255
SpringGreen 8388352
SteelBlue 11829830
Tan 9221330
Teal 8421376
Thistle 14204888
Tomato 4678655
Turquoise 13688896
Violet 15631086
Wheat 11788021
White 16777215
WhiteSmoke 16119285
Yellow 65535
YellowGreen 3329434
————————————————–

Finally, here’s one off-beat (but powerful) example:

IIF("AA" $ upper(contact1->key5).or."BB" $ upper(contact1->key5),-2,1)

It hides the field label (color -2) if it’s not AA or BB. This can be very handy for setting up fluid layouts that change based on the record type without depending on the buggy Record Type feature.

Have you got your own handy expressions? Feel free to add them in the comments area or in the forum!