User manual FRONTRANGE SOLUTIONS GOLDMINE 6.0-ADMINISTRATING

[. . . ] Administrating GoldMine VERSION 6. 0 11/02 ii Table of Contents Copyright Ó 2002 FrontRange Solutions Inc. This software includes software developed by the Apache Software Foundation (http://www. apache. org). The Sentry Spelling-Checker Engine Copyright © 1999 Wintertree Software Inc. GoldMine, HEAT and other FrontRange products and brands are registered trademarks or trademarks of FrontRange Solutions Inc. [. . . ] Setup: Stores additional files for Adobe, BDEShare ®, GoldMine workstation setup, Mdac, and Microsoft® SQL. Temp: Folder to store temporary files. understand databases the data on a server. User involvement or intervention in the management of the data in a SQL Server installation is minimal. 10-6 Understanding GoldMine Databases GoldMines Data Files GoldMine uses three file location designations: GoldDir: Location of the database files such as Calendar files, filters, and other shared data in the default path of \GoldMine\GMBase. For every database you create with GoldMine, there is an equivalent in the Common directory with a given userdefined name. SysDir: Location of the executables, . dlls and . hlp files, and the root of the GoldMine folder. This path may need adjusting if there are access problems to the license, flags, and user files. The SQL Server systems use the same designations for the file groups even though the actual installation is done in a single database. The GM. INI file, found in the main GoldMine folder, contains the paths to these locations: GM. INI for dBASE [GoldMine] GoldDir=x:\apps\GoldMine\GMBase CommonDir=x:\apps\GoldMine\Common SysDir=x:\apps\GoldMine GM. INI for SQL Server [GoldMine] GoldDir=MSSQL: GoldMine_Sales: dbo: CommonDir=MSSQL: GoldMine_Sales: dbo: Note: The SysDir statement line is not required or recommended in an SQL Server installation. UNC path is not recommended for the SysDir because it can cause compression errors during synchronization. If you must use a SysDir statement line, it should be a mapped drive. GoldMines Data Files 10-7 The SQL Server entries do not use paths. The database alias name, GoldMine_Sales, is the BDE entry pointing to the SQL Server databases in use. GoldMine File Locations The following table identifies the locations of the GoldMine files. One set of GMBase tables is created per installation because these tables are typically shared among users. In both dBASE and SQL Server installations, multiple contact data sets are typical. Note: It is extremely important to know the contents of the following table as the information is invaluable when creating Reports or troubleshooting GoldMine. understand databases Use Help>>About>>System to display the About GoldMine dialog box to view the file locations. Note 10-8 Understanding GoldMine Databases GoldMine Files Undocked user default folder Login Tab (Edit/Preferences) GM. INI Commands Tables GMBase GoldMine Database GoldDir= Cal*. Fields5. * Filters. * Forms. * FormsFld. * FormsQue. * GMTLog. * GSFilter GSLogs. * GSServer. * GSSites. * InfoMine. * ImpExp. * LeadDbfs. * Lookup. * Mailbox. * OpMgr. * OpMgrFld. * PerPhone. * Report32. * ResItems. * ScriptsW. SPFiles. * SysLog. * Tracks. * UserLog. * Contact Files Common Default Contact Database CommonDir= Contact1. * Contact2. * ContSupp. * ContHist. * ContGrps. * ContUdef. * ContTlog. * System Files GoldMine GoldMine Home Directory SysDir= Users. * DataDict. * CharSet. * Flags. * License. * SyncLock. * SyncTask. * Tmenu. * Note When working with GoldMine databases hosted to SQL Server and creating custom fields, consult Technical Document 527, Working With Custom Fields in MS SQL. File and Table Types GoldMine has three main database file types for dBASE: *. dbf: Data-holding files. *. mdx: Index files used for optimizing sorting and searching of . dbf file data. GoldMines Data Files 10-9 Structural files hold the specific GoldMine configuration detail, and the data-holding files contain information accumulated about the contacts. Structural Files and Tables Filename. * refers to all files with that name but differing extensions. The tables described on the following pages contain structural files that store data determining how a customized system appears to the end user. The Contact Tables Contact1: GoldMines main database file. This file stores data from the top half of the Contact Record, Summary, and Notes. Each time a new Contact Record is added to GoldMine, it is inserted into Contact1. There is never a case where a record exists in a contact data file without having a matching record in Contact1. Like Contact1, there is one record in Contact2 for each contact in the database. [. . . ] Be sure to extract VRDRUPD. exe on all systems with the problematic VREDIR. vxd. Troubleshooting Meeting Requests to Outside Contacts A-13 Troubleshooting Meeting Requests to Outside Contacts The GoldMine Meeting Request option e-mails meeting request to GoldMine, Outlook, and other iCalendar-enabled applications. You can be the organizer of a meeting, or you can be the recipient of the e-mail meeting request. You can schedule an activity from a Meeting Request received via e-mail from a contact, whether the sender created the activity in GoldMine or another iCalendar-enabled contact management application. You can retrieve the meeting notice just like any other Internet e-mail. [. . . ]