Document #517, Recovering from a GoldBox Import
Covers GoldMine 4.x or higher
The information in this document is provided as-is and is not supported by the FrontRange Solutions GoldMine Technical Support team. The FrontRange Solutions GoldMine Technical Support team does not support the use of third party utilities and/or freeware software. Redstone SoftBase Company has corrected the issue outlined in this document and it is strongly recommended that an upgrade to the latest version of GoldBox be performed prior to importing with GoldBox. Redstone SoftBase can be contacted at 310.441.0782, redstone@earthlink.net, or http://www.redstonesoftbase.com for more information on upgrading to a current version of GoldBox. Upgrading to the current version of GoldBox may avoid the issue outlined in this document entirely.
An issue has been discovered where records imported into GoldMine with an older version of GoldBox may not properly synchronize between copies of GoldMine. If the GoldBox import is prematurely aborted during the import process, GoldBox creates RECID’s with the GoldMine table name that is being imported into instead of the correct encrypted time/date stamp. This results in GoldMine and/or GoldSync evaluating the incorrect RECID (i.e. Contact) as a time/date stamp that places it in the year 2007. During synchronization, a record in this case would not be included in the transfer set that is created.
Checking for the corrupted RECID’s can been done with BR4, BR7, SyncSpy, or an SQL query in GoldMine. BR4 and BR7 are available from Redstone SoftBase as freeware. SyncSpy is available in the Drivers and Downloads section of support.frontrange.com as freeware from FrontRange Solutions. A simple query can also be used in GoldMine, for example:
Select RECID from Contact1
Make sure that none of the RECID’s in the table you are checking matches the table name. If the RECID’s do match the table name, then follow the instructions below.
The following documents, ‘How to Backup Data From GoldMine dBase Installations’ and ‘Performing the Initial Synchronization for a Remote Site’ have information and procedures outlined in them that are referred to in this document.
|
GoldMine Table Names (GMBASE folder) |
Contact File Table Names (COMMON, DEMO, ETC… folders) |
||
|
Cal |
PerPhone |
Lookup |
Contact1 |
|
Fields |
Reports |
SyncSite |
Contact2 |
|
Filters |
Report32 |
MailBox |
ContGrps |
|
FormsFld |
ResItems |
Tracks |
ContHist |
|
Forms |
ScriptSW |
OpMgr |
ContSupp |
|
ImpExp |
SpFiles |
UserLog |
ContUDef |
|
InfoMine |
SyncLog |
OpMgrFLD |
Lookup* |
|
Leaddbf |
SyncProc |
||
|
* Indicates an optional table that may not be present |
|||
It is highly advisable that the individual following this document have an excellent working knowledge of databases and data structures. These changes will require an extensive knowledge of data manipulation in tables, file management in Windows, and an advanced knowledge of GoldMine and GoldSync. The FrontRange Solutions GoldMine Sales team at 800.654.3526 can provide the name of a local GoldMine Authorized Solutions Partner to consult on this matter. This procedure does require un-installing and re-installing GoldMine at all remote locations. The FrontRange Solutions GoldMine Technical Support team can provide instructions on how to re-host an SQL system to dBase in order to properly correct the corrupted RECID’s.
1. Create a complete backup of GoldMine at all remote sites and at the central server. More information on a complete backup is available in the document on ‘How to Backup Data From GoldMine dBase Installations.’Have all remote sites synchronize to a central location and stop addi
2. ng to, modifying, or updating their GoldMine data.
3. At all of the remote locations, the transaction log tables will have to be removed and rebuilt.
a. In the …\GoldMine\GMBase\ folder, remove the GMTLOG.* files.
b. For each Contact set, located in a folder below the …\GoldMine\… folder, affected by the import, remove the CONTLOG.* files.
c. Using GoldMine’s Maintenance Wizard, select the Individual Files option. On the next screen select Contact Set TLogs and Primary Tlogs. On the third screen, select the Rebuild and Pack checkbox and the Verify the data and synchronization information option. Then click on the Next button and the Finish button to complete the process.
4. Have all of the remote locations synchronize all changes to a central location with the Ignore cut-off time option selected or set the Cutoff Date to 1/1/90 to force all changes to be included in the transfer set. This will include all records and ignore the corrupted RECID’s.
5. After all of the remotes have completed synchronization to a central site, create a complete backup of GoldMine. The FrontRange Solutions GoldMine Technical Support team does not support the use of third party utilities and/or freeware software. Using a utility such as BR4, BR7, or GoldBox, globally replace the RECID field in all affected tables with a blank value. It is only necessary to follow these steps for tables that have been imported to improperly by GoldBox. BR4 or BR7 can be used with the following instructions:
a. In Windows on the system with the GoldMine files, select Start>>Run… to open the Run dialog box.
Type Command in the Open: box and select the OK button to open the command window.
b. Change to the folder that contains the affected tables, for example:
CD \Progra~1\GoldMine\GMBase
c. In the command window, open the first affected file on the list by typing
BR4 filename replacing filename with the GoldMine table name and press the Enter key to open BR4 defaulted to the affected table.
d. All commands in BR4 are from the keyboard. To start the replace process, use <Alt-R>. BR4 will prompt for an expression, enter .T. for the expression then press the <Enter> and <Esc> keys.
e. This will bring up a popup list of all fields available for a global replace. Select the RECID field from the list and press <Enter>.
f. BR4 will prompt for an expression again, enter two double quote signs (i.e. “”) for the expression then press the <Enter> and <Esc> keys.
g. When prompted, choose Yes to globally replace the RECID field on every record with a blank value.
h. When BR4 completes the replace operation, it will display the total number of records scanned and replaced. These counts must match the total number of records displayed in the upper right corner by BR4. Press the <Spacebar> to continue.
i. Press the <Esc> and <F2> keys to display a list of the GoldMine tables in BR4 for the currently active folder. Select the next table and then press the <Enter> and <Page Down> keys to view the table in BR4.
j. Repeat steps d through i for all GoldMine tables affected by the improper GoldBox import.
k. Using GoldMine’s Maintenance Wizard, select the Individual Files option. On the next screen select Contact Set TLogs and Primary Tlogs. On the third screen, select the Rebuild and Pack checkbox and the Verify the data and synchronization information option. Then click on the Next button and the Finish button to complete the process. This will give all records in the affected tables a time/date stamp with the current system date.
6. All of the remotes will need to un-install and re-install GoldMine. The un-install can be done with the Add/Remove Programs utility in Windows for GoldMine 4.x or higher. In Windows, select Start>>Settings>>Control Panel to access the utility. If GoldMine does not show in the Add/Remove Programs list, locate and delete the GoldMine folder with Windows Explorer. In a Typical install this is C:\Program Files\GoldMine. It is also recommended to manually confirm that the folder has been removed by the Add/Remove Programs utility prior to reinstallation of GoldMine. This step can be done by the remote locations while the central site is replacing the corrupted RECID’s.
7. After steps 5 and 6 have been completed, all the data will need to be synchronized back to the remote locations with two transfer sets. This procedure is outlined in detail in the document on ‘Performing the Initial Synchronization for a Remote Site.’
The fix outlined in this document will give all of the affected tables RECID’s with the current system time/date. Transfer sets with cutoff dates prior to this date will be much larger than expected and will take longer to transmit to the remote location or user.
Copyright (c) 2002 FrontRange Solutions Inc.
All rights reserved. You may use this document for personal and informational (non-commercial) purposes, provided that the copyright notice and all other notices and permissions appear in all copies, the document is not copied or posted on any network computer or broadcast in any media and modifications are not made to the document. Use for any other purpose is expressly prohibited by law, and may result in civil or criminal penalties.
The information contained in this document is provided “as is” without warranty of any kind. To the maximum extent permitted by applicable law, FrontRange Solutions disclaims all warranties, either express or implied, including warranties for quality, accuracy, merchantability, fitness for a particular purpose, title and non-infringement; and in no event shall FrontRange Solutions or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of profits or data or special damages, even if FrontRange Solutions or its suppliers have been advised of the possibility of such damages.