Bob's Notes - September 2009
9/14/2009 - Sorry about the long lapse; got busy.
Item L, CONTSUPP (E-mail Address) Verify PRIMARIES, is the first item that is written
in green. The use of this color indicates an "active" procedure; that is, one that can
re-write data. In this case, it's a sophisticated procedure that does the following:
1. For each Contact, GoldBox will isolate every E-mail Address record, and determine
whether one--and only one--of them is a Primary E-mail Address.
2. If so, GoldBox does nothing, and goes on to the next Contact.
3. If none is designated as Primary, GoldBox will rewrite the oldest of the records as the
Primary E-mail Address.
4. If more than one is designated as Primary, GoldBox will re-write the records, leaving
the oldest as the one and only Primary E-mail Address.
Items Q and R, Corruption CLEANSE for MASTER/CUSTOM Labels Table
(respectively). Again, the color indicates that GoldBox may write to GoldMine while the
procedures run. The tables in question are ContUDef and Fields5. While there is no
guarantee, this procedure has been found to correct corruption-related display problems
that result from crowding GoldMine fields on the top half of the screen.
Items S and T, U_FIELD Discrepancies and ALIGN w/Fields are designed to detect
(S) and correct (T) any variations that exist between the actual U_ field values, and those
which should exist. I'm not sure how these values would ever get changed, but I have
seen it happen, and this procedure will find and fix 'em.
And finally, there is Item O, which is simply an option to have GoldBox open the file
GX7_Contact_File_VERIFIER.txt when the Verifier has been run from a launch
statement. The Launch button at the top of the interface produces a launch statement
which, when run as a shortcut, will run the Verifier; it will not, however, open the results
file unless Item O has been chosen when the interface was last open.
NEW - October 4, 2009 - There have been important new enhancements to the
Contact File Verifier for GoldBox 7 (only). Now, in addition to Item O's text report, CFV will
produce a dBase table that contains the Recid, Accountno and other useful
information about every record that was found to be an exception, in every GoldMine
table.
For example, if you checked Item I (Linked Docs) before running the CFV, GoldBox will
check every Linked Doc record in GoldMine to make sure it has a valid Accountno, AND it
will check to see whether a document actually exists with the indicated filename, at the
indicated location. Any Linked Doc record that does not pass all these tests will become
an exception record in the table CONVERFY.DBF Other types of GoldMine records will
be associated with other tests, as appropriate.
This new table will, by default, be presented upon completion of the Contact File Verifier
run; and the table for the most recent run will always be available as a selection under
GoldBox 7's Data menu item. If you want to keep a permanent record of every
CONVERFY.DBF that's produced, you can export it before closing, giving it a unique
name.
By producing this table, GoldBox minimizes the possible need to run queries to delete, or
otherwise manage, exceptions. GoldBox creates a filterable table that you can use for
whatever kind of post-report processing that you want to do...a big time saver!
However, if you don't want to spend the small amount of extra processing time required to
produce this table, GoldBox gives you an opt-out checkbox, Item V on the CVF interface.
Just uncheck the box, and the table will not be populated or displayed.
Another new feature of the CFV is that it now displays the number of Contact1 and
Contact2 records in the GoldMine database as soon as the CFV interface opens. This is
so you can decide whether you have time to run the procedure at the moment. If there's a
large number of GoldMine records, you may want to wait until later. Due to the complexity
of the things it does, the CFV does NOT offer a "bail out" option, and it should be run,
undisturbed, until completion.
One final new option is Item Z which will, when checked, cause the CVF to run in a
minimized condition, thus significantly increasing the speed with which it runs...another
good option, if you have a large number of records in GoldMine.
Here is a screenshot of the CONVERFY.DBF table, with the CVF text report, and
GoldMine, in the background:
Item L, CONTSUPP (E-mail Address) Verify PRIMARIES, is the first item that is written
in green. The use of this color indicates an "active" procedure; that is, one that can
re-write data. In this case, it's a sophisticated procedure that does the following:
1. For each Contact, GoldBox will isolate every E-mail Address record, and determine
whether one--and only one--of them is a Primary E-mail Address.
2. If so, GoldBox does nothing, and goes on to the next Contact.
3. If none is designated as Primary, GoldBox will rewrite the oldest of the records as the
Primary E-mail Address.
4. If more than one is designated as Primary, GoldBox will re-write the records, leaving
the oldest as the one and only Primary E-mail Address.
Items Q and R, Corruption CLEANSE for MASTER/CUSTOM Labels Table
(respectively). Again, the color indicates that GoldBox may write to GoldMine while the
procedures run. The tables in question are ContUDef and Fields5. While there is no
guarantee, this procedure has been found to correct corruption-related display problems
that result from crowding GoldMine fields on the top half of the screen.
Items S and T, U_FIELD Discrepancies and ALIGN w/Fields are designed to detect
(S) and correct (T) any variations that exist between the actual U_ field values, and those
which should exist. I'm not sure how these values would ever get changed, but I have
seen it happen, and this procedure will find and fix 'em.
And finally, there is Item O, which is simply an option to have GoldBox open the file
GX7_Contact_File_VERIFIER.txt when the Verifier has been run from a launch
statement. The Launch button at the top of the interface produces a launch statement
which, when run as a shortcut, will run the Verifier; it will not, however, open the results
file unless Item O has been chosen when the interface was last open.
NEW - October 4, 2009 - There have been important new enhancements to the
Contact File Verifier for GoldBox 7 (only). Now, in addition to Item O's text report, CFV will
produce a dBase table that contains the Recid, Accountno and other useful
information about every record that was found to be an exception, in every GoldMine
table.
For example, if you checked Item I (Linked Docs) before running the CFV, GoldBox will
check every Linked Doc record in GoldMine to make sure it has a valid Accountno, AND it
will check to see whether a document actually exists with the indicated filename, at the
indicated location. Any Linked Doc record that does not pass all these tests will become
an exception record in the table CONVERFY.DBF Other types of GoldMine records will
be associated with other tests, as appropriate.
This new table will, by default, be presented upon completion of the Contact File Verifier
run; and the table for the most recent run will always be available as a selection under
GoldBox 7's Data menu item. If you want to keep a permanent record of every
CONVERFY.DBF that's produced, you can export it before closing, giving it a unique
name.
By producing this table, GoldBox minimizes the possible need to run queries to delete, or
otherwise manage, exceptions. GoldBox creates a filterable table that you can use for
whatever kind of post-report processing that you want to do...a big time saver!
However, if you don't want to spend the small amount of extra processing time required to
produce this table, GoldBox gives you an opt-out checkbox, Item V on the CVF interface.
Just uncheck the box, and the table will not be populated or displayed.
Another new feature of the CFV is that it now displays the number of Contact1 and
Contact2 records in the GoldMine database as soon as the CFV interface opens. This is
so you can decide whether you have time to run the procedure at the moment. If there's a
large number of GoldMine records, you may want to wait until later. Due to the complexity
of the things it does, the CFV does NOT offer a "bail out" option, and it should be run,
undisturbed, until completion.
One final new option is Item Z which will, when checked, cause the CVF to run in a
minimized condition, thus significantly increasing the speed with which it runs...another
good option, if you have a large number of records in GoldMine.
Here is a screenshot of the CONVERFY.DBF table, with the CVF text report, and
GoldMine, in the background:
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
