The GoldMine Blog - Tips, Tricks & More

January 2, 2008 (Version 2008-A for GoldBox-7 / GoldBox-SQL / GoldBox-5)
 
ENHANCED:  Import / Update.  When importing into or updating Main Contacts, you can now select a global switch to turn OFF the Plug-in of TAB records.  Especially useful for TESTING matching scenarios to Main Contacts, typically used in conjunction with the Bypass Matches checkbox.
 
ENHANCED:  Import / Update.  You can now use Quick-Delete (RECID-based matching) for the CONTACT2 table (user-defined fields for Main Contact).  This can be used in conjunction with the new Preview option at Table Dedupe.  See below.
 
ENHANCED:  Import / Update.  When importing into GoldMine, you can now click a button to instantly 'park' 5 Source records into GXI.DBF.  Button is QUIK PARK, at Import Setup screen, Source section.  This option works directly, and does not require you to select the PARK and STOP checkbox.
 
ENHANCED:  Import / Update.  When importing into GoldMine with GoldBox-7 or GoldBox-SQL, the Direct SQL Query button will now allow you, at the Query Builder, to directly build Merge Field expressions from GXI.DBF and easily append them to your SQL Query.   You will be able to Interpret them, and test the Result of the SQL Query while still in Import Setup mode.  See next.
 
ENHANCED: SQL Query Builder.  A new purple button called {INTERPRET} has been added.  If you are using Merge Fields or GXinput() fragments in your SQL Query, this option will do an onscreen interpretation in the SQL Query.  In addition, if you wish to run the SQL Query at the GoldBox interface and you have Merge Field fragments, you can Double-Right-Click the RESULT button to interpret the fragments for your Result Set.  Especially useful for the VLinkByQuery() function.
 
ENHANCED: Function VLinkByQuery().  You can now use Merge Field expressions directly in the SQL Query.  The Assembler (at the Service Menu) has been altered to make the creation and appending of Merge Field expressions easier.  VLinkByQuery() is similar to VLink2dBase(), whereby you can dynamically link to a GoldMine or outside ODBC table during a GoldBox batch operation (such as Export, Import, Global Replace, Group Builder, etc.)
 
FIXED: Bug with {Fetch RECID matching for Tab record Import/Update} in GoldBox-7, which uses the above VLinkByQuery() logic.
 
ENHANCED: Single Table Dedupe.  You can now cause the identified Dupes to be exported out to a dBase table called GOLDDUPE.DBF, instead of deleting.  Ideal for archiving Dupes before deletion, and to use for comparing to GoldMine.  For GoldMine tables containing the ACCOUNTNO field, you can open GOLDDUPE.DBF in the GXBrowser, where a DDE Link is attempted to GoldMine (if open).  NOTE: For GoldBox-5 and GoldBox-SQL, Single Table Dedupe is only in the PRO Edition.
 
ENHANCED: Merge-Purge.  When creating a new setup, GoldBox auto-inserts a matching scheme of Smoothed Companies and Smoothed Contact Names.  GoldBox will now add the 2nd limiting parameter of 'C' to the SmoothComp() function call, to limit searches to Company entries only.  NOTE: The inserted matching scheme is only a suggested entry, and can be easily changed to whatever matching scheme you wish.
 
ENHANCED: Config Screen for GoldBox-7.  Intended to make initial configuration a bit easier. 

Update is available for download at: http://www.redstonesoftbase.com/index_00000a.htm 

To use simply go to Lookup | SQL Queries then copy and paste into the top-half of the screen and hit query.  

First, all primary contacts and their primary email address…

select contact1.company, contact1.contact, contsupp.contsupref from contact1, contsupp where contact1.accountno = contsupp.accountno and contsupp.contact = 'E-mail Address' and contsupp.zip like '_1__%' order by contact1.company, contact1.contact

Second, all secondary contacts and their email addresses…

select contact1.company, contsupp.contact, contsupp2.contsupref from contact1, contsupp, contsupp as contsupp2 where contsupp.rectype = 'C' and contact1.accountno = contsupp.accountno and contsupp.recid = contsupp2.linkacct order by contact1.company, contsupp.contact

Third,  all the email address for primary and secondary together… This will work only on SQL systems…

select contact1.company, contact1.contact, contsupp.contsupref, contact1.accountno from contact1, contsupp where contact1.accountno = contsupp.accountno and contsupp.contact = 'E-mail Address' and contsupp.zip like '_1__%'
union
select contact1.company, contsupp.contact, contsupp2.contsupref, contact1.accountno from contact1, contsupp, contsupp as contsupp2 where contsupp.rectype = 'C' and contact1.accountno = contsupp.accountno and contsupp.recid = contsupp2.linkacct order by contact1.company

Fourth, all records without an email addresses…

select company, contact from contact1 where accountno not in (select accountno from contsupp where contact = 'E-mail Address' and rectype = 'P') order by company, contact

You can bet this is going to end up on my Top 10 List in December!

It’s a question/complaint I get asked at least once a week. 

By default, after you complete an activity it will no longer appear on the calendar.  Sure, it appears on the contact’s record, but it no longer appears on the calendar!

… It’s There!



Then you complete the activity, and now, it’s not!



What Insanity!?!

Fortunately, changing this is just a couple of click away.  First, Right-Click within the Calendar and choose Activities.



Next, check the types of completed activities you wish to display.  This list is on the right side of the window.

I prefer to show everything except Messages and Others.



Click OK, and voila!  



The completed activities show up with a gray background, with a line crossing out the contact/company and reference!

For more on customizing the calendar check out this posting on what the calendar displays…

http://www.thegmblog.com/2006/12/customizing_your_calendar_disp.php

Few things annoy me more, than someone who has entered a contact into GoldMine with improper capitalization in the contact field, address field, city, etc…  

Here’s a trick for giving those field values ‘proper’ capitalization without having to do any typing!

In the Field’s Lookup add an entry like you see below… Just swap out contact for the field… Company, address1, etc.

Then, on a field w/ improper capitalization select the lookup code… and Voila!

You’ll also notice in the Setup for fields within the Lookup window you can choose Capitalize first letter.  Not a bad option to turn on either.  

 

PS - Also check out the Dear field post: http://www.thegmblog.com/2007/08/how_to_use_the_dear_field_in_g.php