ACT! Software Development Kit (SDK)
Technical
Reference Guide
ACT! Database File Formats Reference appendix
Appendix A ACT! Database File Formats Reference
Overview of ACT!
Database Files.................................................................................... 491
ACT! database table relationships....................................................................... 495
What’s New ...................................................................................................................... 496
Changes for ACT! 4.0......................................................................................... 496
Changes for ACT! 2000....................................................................................... 496
Looking at ACT! Database Tables................................................................................... 496
Activity table (.ADB) fields.................................................................................. 496
Contact table (.DBF) fields.................................................................................. 501
E-mail table (.EDB) fields................................................................................... 508
Group table (.GDB) fields.................................................................................... 509
List table (.DDB) fields (requires ACT! 2000 or later).............................................. 513
Notes/History table (.HDB) fields......................................................................... 514
Relational table (.REL) fields............................................................................... 517
Understanding the Relational table................................................................ 518
Sales table (.SDB) fields (ACT! 2000 or later)....................................................... 519
APPENDIX
ACT! Database
File Formats Reference
This appendix describes the file formats of ACT!TM database tables and the relationships between the tables in ACT! 3.0 or later. It provides technical information on ACT! tables and the fields within records in each table. This information is provided to assist in developing applications that work with ACT! databases. Using the ACT! OLE Database Object is the recommended method of reading and writing information to ACT! databases.
The ACT! database is a collection of files used to store information that is entered by the user. This collection of files consists of tables that store contact, group, activity, notes and history, e-mail, and other information. The Relational table stores links that allow this information to be accessible in associated tables within the ACT! application. ACT! 3.0 or later uses standard FoxPro formatted tables.
The following table describes ACT! database files based on their extensions.
Extension |
Description |
.ADB |
Activity table |
.ADX |
Index file for the Activity (.ADB) table |
.BLB |
Binary Large Object Database (BLOB) file |
.DBF |
Contact table |
.DDB |
List table for the Sales (.SDB) table (in ACT! 2000 or later databases) |
.DDF |
Database definition file |
.DDX |
Index file for the List (.DDB) table (in ACT! 2000 or later databases) |
.EDB |
E-mail table |
.EDX |
Index file for the E-mail (.EDB) table |
.GDB |
Group table |
.GDX |
Index file for the Group (.GDB) table |
.HDB |
Notes/History table |
.HDX |
Index file for the Notes/History (.HDB) table |
.LCK |
Record locking file for ACT! multi-user databases |
.MDX |
Index file for the Contact (.DBF) table |
.REL |
Relational table for ACT! tables |
.REM |
Reminders file (in ACT! 2000 or later databases) |
.REX |
Index file for the Relational (.REL) table |
.SDB |
Sales table (in ACT! 2000 or later databases) |
.SDX |
Index file for the Sales (.SDB) table (in ACT! 2000 or later databases) |
.TDB |
Transaction synchronization log table |
.TDX |
Index file for the Transaction synchronization log (.TDB) table |
.TLx |
Record locking file for ACT! multi-user databases on a network, where x is the number of each subsequent file (TL1, TL2, and so on) |
The
following list provides brief descriptions of ACT! database tables and an
overview of data relationships within ACT! tables.
Activity (.ADB) Contains records for call, meeting, and to-do activities. Activity records are identified by a Unique ID and an activity type. Activity records are linked to contact records by Relational table records and to group records by a Unique ID.
Binary Large Object Database (.BLB) Contains variable size data including attachment file and path names, database user information, drop-down list information, e‑mail addresses, notes and history regarding text, recurring activity information, and synchronization settings. ACT! database tables contain references as links to a Binary Large Object Database file.
Contact (.DBF) Contains contact information. Contact records are identified by a Unique ID and linked with an ACT! database user by the User Name.
Database Definition File (.DDF) Stores field definition information including mapping of ACT! field names to ACT! database schema names, index file structures, and references to drop-down list items in the Binary Large Object Database (.BLOB) file.
E-mail (.EDB) Contains the e-mail address and e-mail system information that is displayed in the Contact window. E-mail records are identified and linked to contact records by the Contact Unique ID field. E-mail addresses are stored in the Binary Large Object Database file.
Group (.GDB) In ACT! 3.0 or later, contains separate records each with their own histories, notes, and attachments. Group records are identified by a Unique ID and linked with an ACT! database user by the User Name. Group records are linked to contact records by records in the Relational table.
List (.DDB) In ACT! 2000 or later, contains product, product type, and main competitor data linked to the Sales table. The Sales table stores a Unique ID for the field containing each of these three types of data. List records are identified and linked to sales records by the List table Unique ID field.
Notes/History (.HDB) Contains notes, histories, and attachments. Note, history, and attachment records are identified by a Unique ID. Notes/History records and attachments are linked to contact and group records by Unique ID fields in Notes/History table records.
Record locking file (.LCK) The Record locking file for ACT! multi-user databases.
Relational table (.REL) The Relational table is used in ACT! 3.0 or later to link contact, group, and activity table records.
Reminders file (.REM) Contains ACT! reminders data supplied by the system.
Sales (.SDB) In ACT! 2000 or later, contains sales information. Sales records are identified by a Unique ID. Sales records are linked to contact and group records and data in the List table by Unique ID fields in Sales table records.
Transaction Synchronization Log (.TDB) Records the fields that are changed in an ACT! database and the date and the time of the change for synchronization with another database.
The following diagram shows each table in an ACT! and shows how these tables are linked, including links to the Relational table.
ACT! database table fields also link to data stored in the Binary Large Object Database (BLOB) file.
The Unique ID field contains a 12 character value that is derived from the current date and time, then translated into a unique sequence of alphanumeric and special characters that can be displayed.
This section describes changes for ACT! 4.0 and ACT! 2000.
The Ticker Symbol field in the Contact table and record type 102 for the new E-mail record type in the Notes/History table have been added for ACT! 4.0. Indexes have been added for the additional Company and Phone columns in the Task List. In ACT! 4.0, the E-mail system is a preference and is stored in the Windows registry instead of being stored in the E-mail table as in ACT! 3.0.
The List table, Sales table, and the Reminders file have been added for ACT! 2000. The following fields have been added to the Activity table: Details, External Id, and Record Status. The following fields have been added to the Group table: Group Level, Industry, Number of Employees, Parent ID, Referred By, Region, Revenue, SIC Code, Ticker Symbol, and Web Site.
The tables in this section show database schema information for each field in every ACT! database table. This includes field names, database schema names, field formats, and field lengths. The tables also show the field ID values and the corresponding field constants to use to read and write data to ACT! database fields using the ACT! OLE Database Object and the ACT! OLE Application Object.
Added user-defined fields start numbering at Unique ID type 1000. Also, any field whose Unique ID type is between 200 and 999 is a virtual field that is read-only. Virtual fields reference a calculated value, a portion of a field in the same table, or a field in another table of file.
The following table shows database schema information for each field in an ACT! database Activity table.
Field name |
Database |
Format/ |
Field |
Field constant |
Description |
Alarm Status |
ALRMSTATUS |
Num |
33 |
AF_AlarmStatus |
Alarm status for the activity. |
Banner Color |
BANNER_CLR |
Num |
34 |
AF_BannerColor |
Code for the activity color. |
Cleared Status |
CLEARED |
Num |
41 |
AF_ClearedStatus |
Specifies if the activity was
cleared. |
Contact Count |
CONT_CNT |
Num |
100 |
AF_TotalInActivity |
Total number of contacts with whom the activity is scheduled. This field is supplied by the system. |
Create Timestamp |
CTIME |
Char |
2 |
AF_CreateTimestamp |
Date and time the activity record was created. This field is supplied by the system and stored in a compressed format. |
Date/Time |
START_TIME |
Char |
28 |
AF_StartTime |
Start date and time of the activity. The format is YYYYMMDDHHMM. The default is the current system date and time. |
Details |
DETAILS |
Char |
45 |
AF_Details |
Contains a description of the details associated with the activity for ACT! 2000 or later databases only. This 6-byte field is supplied by the system and contains a reference to a field in the Binary Large Object Database file that contains a maximum of 32,768 characters. |
Duration |
DURATION |
Num |
30 |
AF_Duration |
Duration of the activity in minutes. |
Edit Timestamp |
ETIME |
Char |
3 |
AF_EditTimestamp |
Date and time the activity record was last modified. The initial value is the date and time the activity record was created. This field is supplied by the system and stored in a compressed format. |
E-mail Status |
EML_STATUS |
Num |
35 |
AF_EmailStatus |
Specifies if an e-mail reminder will be sent for the
activity. |
End Time |
END_TIME |
Char |
29 |
AF_EndTime |
Calculated end date and time for the activity. The format is YYYYMMDDHHMM. This field is supplied by the system. |
Exception Date |
EXCEPTDATE |
Char |
44 |
AF_ExceptionDate |
Original date of an exception instance of a recurring activity. The format is YYYYMMDDHHMM. |
External Id |
EXTERNID |
Char |
47 |
AF_ExternalId |
Contains the record ID of an activity record in an external database (Outlook) in ACT! 2000 or later databases only. |
Group |
GROUPID |
Char |
39 |
AF_GroupId |
The Unique ID of the group record to which the activity record is associated. This field is supplied by the system. |
Lead Time |
LEAD_TIME |
Num |
32 |
AF_LeadTime |
Advance notice for the activity alarm in minutes. The default lead time for the activity is used if the alarm is not set. |
Merge Timestamp |
MTIME |
Char |
4 |
AF_MergeTimestamp |
Date and time the activity record was imported into ACT! or synchronized with another ACT! database. This field is supplied by the system and stored in a compressed format. |
Priority |
PRIORITY |
Num |
26 |
AF_Priority |
Priority of the activity. |
Public/Private |
PUB_STATUS |
Num |
5 |
AF_PublicPrivate |
Specifies if the activity is public or private. |
Record Status |
RECSTATUS |
Num |
46 |
AF_RecordStatus |
Specifies if the record was imported from or exported to an external database (Outlook), in ACT! 2000 or later databases only. |
Recurring Exceptions |
EXCEPTIONS |
Char |
43 |
AF_Exceptions |
A list of dates for exception instances of a recurring activity. This 6-byte field is supplied by the system and contains a reference to data stored in the Binary Large Object Database file. |
Recurring Identifier |
RECURID |
Char |
42 |
AF_RecurringId |
For recurring activities, contains the Unique ID of the parent activity if this instance of the recurring activity has been changed. Otherwise this field is blank. This field is supplied by the system. |
Recurring Map |
RECURRING |
Char |
36 |
AF_Recurring |
Recurring activity settings of: |
Regarding |
REGARDING |
Char |
27 |
AF_Regarding |
Description of the activity. |
Scheduled By |
SCHEDL_BY |
Char |
38 |
AF_ScheduledBy |
User ID of the database user who scheduled the activity. The default is the logged-on user. This field is supplied by the system. |
Scheduled Date |
— |
Char |
200 |
AVF_ScheduledDate |
Date portion of the date and time for which the activity is scheduled. The format is YYYYMMDD. This field references the Date/Time field and is read-only. |
Scheduled For |
SCHEDL_FOR |
Char |
37 |
AF_ScheduledFor |
User ID of the database user for whom the activity is scheduled. The default is the logged-on user. This field is supplied by the system. |
Scheduled Time |
— |
Char |
201 |
AVF_ScheduledTime |
Time portion of the date and time for which the activity is scheduled. The format is HHMM. This field references the Date/Time field and is read-only. |
Scheduled With |
SCHEDLWITH |
Char |
40 |
AF_FirstScheduledWith |
User ID of the contact displayed in the Calendar, Activities tab, and Task List for the activity. This field is supplied by the system. |
Timeless Status |
TM_STATUS |
Num |
31 |
AF_TimelessStatus |
Timeless status for the start time of the activity. |
Total Duration |
TDURATION |
Num |
101 |
AF_TotalDuration |
Total number of minutes from the start time of the first instance of the activity to the ending time of the last instance of the activity, minus one minute. |
Type |
TYPE |
Num |
25 |
AF_Type |
Activity record type. |
Unique Id |
UNIQUE_ID |
Char |
1 |
AF_UniqueID |
Unique activity record identification number. This field is supplied by the system. |
The following table shows database schema and Contact window information for each field in an ACT! database Contact table.
Field name |
Database |
Format/ |
Field |
Field |
Description |
2nd Contact |
NAME2 |
Char |
72 |
CF_Name2 |
Second contact’s name. |
2nd Last Reach |
ALT1REACH |
Char |
92 |
CF_Alt1Reach |
Date of the last completed call to the second contact. The format is YYYYMMDD. This field is supplied by the system. |
2nd Phone |
PHONE2 |
Char |
74 |
CF_Phone2 |
Second contact’s phone number. |
2nd Phone Ext. |
PHONE2_EXT |
Char |
83 |
CF_Phone2Ext |
Extension for the second contact’s phone number. |
2nd Title |
TITLE2 |
Char |
73 |
CF_Title2 |
Second contact’s title. |
3rd Contact |
NAME3 |
Char |
75 |
CF_Name3 |
Third contact’s name. |
3rd Last Reach |
ALT2REACH |
Char |
93 |
CF_Alt2Reach |
Date of the last completed call to the third contact. The format is YYYYMMDD. This field is supplied by the system. |
3rd Phone |
PHONE3 |
Char |
77 |
CF_Phone3 |
Third contact’s phone number. |
3rd Phone Ext. |
PHONE3_EXT |
Char |
84 |
CF_Phone3Ext |
Extension for the third contact’s phone number. |
3rd Title |
TITLE3 |
Char |
76 |
CF_Title3 |
Third contact’s title. |
Address 1 |
ADDR1 |
Char |
27 |
CF_Address1 |
First line of the contact’s primary address. |
Address 2 |
ADDR2 |
Char |
28 |
CF_Address2 |
Second line of the contact’s primary address. |
Address 3 |
ADDR3 |
Char |
29 |
CF_Address3 |
Third line of the contact’s primary address. |
Alt Phone |
ALTPHONE |
Char |
71 |
CF_AltPhone |
Contact’s alternate phone number. |
Alt Phone Ext. |
ALTEXT |
Char |
82 |
CF_AltPhoneExt |
Extension for the contact’s alternate phone number. |
Assistant |
ASSISTANT |
Char |
47 |
CF_Assistant |
Name of the contact’s assistant. |
Asst. Phone |
ASST_PHONE |
Char |
86 |
CF_AsstPhone |
Phone number of the contact’s assistant. |
Asst. Phone Ext. |
ASST_EXT |
Char |
87 |
CF_AsstExt |
Extension for the phone number of the contact’s assistant. |
Asst. Title |
ASST_TITLE |
Char |
85 |
CF_AsstTitle |
Title of the contact’s assistant. |
City |
CITY |
Char |
30 |
CF_City |
City in the contact’s address. |
Company |
COMPANY |
Char |
25 |
CF_Company |
Contact’s company name. |
Contact |
NAME |
Char |
26 |
CF_Name |
Contact’s name. |
Contact Type |
CONT_TYPE |
Num |
125 |
CF_ContactType |
Contact record type. |
Country |
COUNTRY |
Char |
33 |
CF_Country |
Country in the contact’s address. |
Create Timestamp |
CTIME |
Char |
2 |
CF_CreateTimestamp |
Date and time the contact record was created. This field is supplied by the system and stored in a compressed format. |
Department |
DEPARTMENT |
Char |
88 |
CF_Department |
Contact’s department. |
Edit Timestamp |
ETIME |
Char |
3 |
CF_EditTimestamp |
Date and time the contact record was last modified. This field is supplied by the system and stored in a compressed format. |
Email Address |
— |
Char |
200 |
CVF_EmailAddress |
The primary e-mail address for the contact. This field references the Logon field in the E-mail table for ACT! 4.0 or later databases only and is read-only. |
Email Carrier |
— |
Char |
203 |
CVF_EmailCarrier |
The e-mail Carrier portion of the primary e-mail address for the contact. This field references the Carrier field in the E-mail table for ACT! 3.0 databases only and is read-only. |
Email Logon |
— |
Char |
202 |
CVF_EmailLogon |
The e-mail Logon portion of the primary e-mail address for the contact. This field references the Logon field in the E-mail table for ACT! 3.0 databases only and is read-only. |
Fax |
FAX |
Char |
36 |
CF_Fax |
Contact’s fax number. |
Fax Ext. |
FAX_EXT |
Char |
81 |
CF_FaxExt |
Extension for the contact’s fax number. |
First Name |
FNAME |
Char |
78 |
CF_FirstName |
Contact’s first name. This field is parsed by the system from the contact. |
Home Address 1 |
ALTADDR1 |
Char |
65 |
CF_AltAddress1 |
First line of the contact’s home address. |
Home Address 2 |
ALTADDR2 |
Char |
66 |
CF_AltAddress2 |
Second line of the contact’s home address. |
Home City |
ALTCITY |
Char |
67 |
CF_AltCity |
City in the contact’s home address. |
Home Country |
ALTCOUNTRY |
Char |
70 |
CF_AltCountry |
Country in the contact’s home address. |
Home Phone |
HOME_PHONE |
Char |
37 |
CF_HomePhone |
Contact’s home phone number. |
Home State |
ALTSTATE |
Char |
68 |
CF_AltState |
State in the contact’s home address. |
Home Zip |
ALTZIP |
Char |
69 |
CF_AltZip |
ZIP code in the contact’s home address. |
ID/Status |
IDSTATUS |
Char |
34 |
CF_IDStatus |
Category assigned to the contact. |
Last Attempt |
LAST_ATMPT |
Char |
43 |
CF_LastAttempt |
Date of the last attempt to call the contact. The format is YYYYMMDD. This field is supplied by the system. |
Last Meeting |
LAST_MEET |
Char |
41 |
CF_LastMeet |
Date of the last meeting with the contact. The format is YYYYMMDD. This field is supplied by the system. |
Last Name |
LNAME |
Char |
79 |
CF_LastName |
Contact’s last name. This field is parsed by the system from the contact name. |
Last Reach |
LAST_REACH |
Char |
42 |
CF_LastReach |
Date of the last completed call to the contact. The format is YYYYMMDD. This field is supplied by the system. |
Last Results |
LAST_RSLTS |
Char |
48 |
CF_LastResults |
Comments on the last results with the contact. |
Letter Date |
LTTR_DATE |
Char |
44 |
CF_LetterDate |
Date of the last letter sent to the contact. The format is YYYYMMDD. This field is supplied by the system. |
Merge Timestamp |
MTIME |
Char |
4 |
CF_MergeTimestamp |
Date and time the contact record was imported into ACT! or synchronized with another ACT! database. This field is supplied by the system and stored in a compressed format. |
Mobile Phone |
MOBILPHONE |
Char |
38 |
CF_MobilePhone |
Contact’s mobile phone number. |
Note |
— |
Char |
201 |
CVF_Note |
This field is obsolete and is supplied for backward-compatibility with ACT! 2.0 databases. |
Owner |
OWNER |
Char |
91 |
CF_UsersCompany |
The company name of the database user who created the contact record. |
Pager |
PAGER |
Char |
39 |
CF_Pager |
Contact’s pager number. |
Phone |
PHONE |
Char |
35 |
CF_Phone |
Contact’s primary phone number. |
Phone Ext. |
EXT |
Char |
80 |
CF_Ext |
Extension for the contact’s primary phone number. |
Public/Private |
PUB_STATUS |
Num |
5 |
CF_PublicPrivate |
Access level for the contact. |
Record Creator |
CREATOR |
Char |
90 |
CF_Creator |
The database user who created the contact record. This field is supplied by the system. |
Record Manager |
USER |
Char |
6 |
CF_RecordManager |
The Unique ID of the database user permitted to access and change the status of private contacts. This field is supplied by the system. |
Referred By |
REFER_BY |
Char |
49 |
CF_ReferredBy |
Description of the contact’s referral source. |
Salutation |
SALUTATION |
Char |
40 |
CF_Salutation |
Contact’s letter salutation or greeting name. |
Spouse |
SPOUSE |
Char |
89 |
CF_Spouse |
Name of the contact’s spouse. |
State |
STATE |
Char |
31 |
CF_State |
State in the contact’s address. |
Ticker Symbol |
TICKERSYM |
Char |
95 |
CF_TickerSymbol |
Company’s stock ticker symbol for ACT! 4.0 or later databases only. |
Title |
TITLE |
Char |
46 |
CF_Title |
Contact’s title. |
Unique Id |
UNIQUE_ID |
Char |
1 |
CF_UniqueID |
Unique contact record identification number. This field is supplied by the system. |
User 1 |
USER1 |
Char |
50 |
CF_User1 |
User-definable field 1. |
User 2 |
USER2 |
Char |
51 |
CF_User2 |
User-definable field 2. |
User 3 |
USER3 |
Char |
52 |
CF_User3 |
User-definable field 3. |
User 4 |
USER4 |
Char |
53 |
CF_User4 |
User-definable field 4. |
User 5 |
USER5 |
Char |
54 |
CF_User5 |
User-definable field 5. |
User 6 |
USER6 |
Char |
55 |
CF_User6 |
User-definable field 6. |
User 7 |
USER7 |
Char |
56 |
CF_User7 |
User-definable field 7. |
User 8 |
USER8 |
Char |
57 |
CF_User8 |
User-definable field 8. |
User 9 |
USER9 |
Char |
58 |
CF_User9 |
User-definable field 9. |
User 10 |
USER10 |
Char |
59 |
CF_User10 |
User-definable field 10. |
User 11 |
USER11 |
Char |
60 |
CF_User11 |
User-definable field 11. |
User 12 |
USER12 |
Char |
61 |
CF_User12 |
User-definable field 12. |
User 13 |
USER13 |
Char |
62 |
CF_User13 |
User-definable field 13. |
User 14 |
USER14 |
Char |
63 |
CF_User14 |
User-definable field 14. |
User 15 |
USER15 |
Char |
64 |
CF_User15 |
User-definable field 15. |
Web Site |
URL |
Char |
94 |
CF_URL |
Contact’s web site URL address. |
Zip |
ZIP |
Char |
32 |
CF_Zip |
ZIP code in the contact’s address. |
The following table shows database schema information for each field in an ACT! database E-mail table. An e-mail record is created for each e-mail address for a contact.
Field name |
Database |
Format/ |
Field |
Field constant |
Description |
Contact |
CONTACTID |
Char |
28 |
EF_ContactId |
The Unique ID of the contact record with which the e-mail record is associated. This field is supplied by the system. |
Create Timestamp |
CTIME |
Char |
2 |
EF_CreateTimestamp |
Date and time the e-mail record was created. This field is supplied by the system and stored in a compressed format. |
Edit Timestamp |
ETIME |
Char |
3 |
EF_EditTimestamp |
Date and time the e-mail record was last modified. The initial value is the date and time the e-mail record was created. This field is supplied by the system and stored in a compressed format. |
Logon |
LOGON |
Char |
25 |
EF_Logon |
The e-mail address. This 6-byte field is supplied by the system and contains a reference to the Binary Large Object Database file. |
Carrier |
CARRIER |
Char |
26 |
EF_Carrier |
The e-mail system for the e-mail address in this record. This field is blank in ACT! 4.0 or later databases. In ACT! 4.0 or later, the e-mail system is a preference and is stored in the Windows registry. |
Merge Timestamp |
MTIME |
Char |
4 |
EF_MergeTimestamp |
Date and time the e-mail record was imported into ACT! or synchronized with another ACT! database. This field is supplied by the system and stored in a compressed format. |
Primary Status |
PRM_STATUS |
Num |
27 |
EF_PrimaryStatus |
E-mail record status. |
Unique Id |
UNIQUE_ID |
Char |
1 |
EF_UniqueID |
Unique e-mail record identification number. This field is supplied by the system. |
The following table shows database schema and Group window information for each field in an ACT! database Group table.
Field name |
Database |
Format/ |
Field |
Field constant |
Description |
Address 1 |
ADDR1 |
Char |
27 |
GF_Address1 |
First line of the group’s address. |
Address 2 |
ADDR2 |
Char |
28 |
GF_Address2 |
Second line of the group’s address. |
Address 3 |
ADDR3 |
Char |
29 |
GF_Address3 |
Third line of the group’s address. |
City |
CITY |
Char |
30 |
GF_City |
City in the group’s address. |
Contact Count |
CONT_CNT |
Num |
100 |
GF_TotalInGroup |
Total number of contacts in the group. |
Country |
COUNTRY |
Char |
33 |
GF_Country |
Country in the group’s address. |
Create Timestamp |
CTIME |
Char |
2 |
GF_CreateTimestamp |
Date and time the group record was created. This field is supplied by the system and stored in a compressed format. |
Description |
DESCRPTION |
Char |
40 |
GF_Description |
Description of the group. |
Division |
DIVISION |
Char |
26 |
GF_Division |
Division for the group. |
Edit Timestamp |
ETIME |
Char |
3 |
GF_EditTimestamp |
Date and time the group record was last modified. This field is supplied by the system and stored in a compressed format. |
Group Level |
GRPLEVEL |
Num |
56 |
GF_GroupLevel |
The level of the group (a parent group or a subgroup) for
ACT! 2000 or later databases only. |
Group Name |
GRP_NAME |
Char |
25 |
GF_Name |
Name of the group. |
Industry |
INDUSTRY |
Char |
58 |
GF_Industry |
Type of industry for the group for ACT! 2000 or later databases only. |
Merge Timestamp |
MTIME |
Char |
4 |
GF_MergeTimestamp |
Date and time the group record was imported into ACT! or synchronized with another ACT! database. This field is supplied by the system and stored in a compressed format. |
Note |
— |
Char |
200 |
GVF_Note |
This field is obsolete and is supplied for backward-compatibility with ACT! 2.0 databases. |
Number of Employees |
EMPLOY |
Num |
60 |
GF_Employees |
Number of employees in the group for ACT! 2000 or later databases only. |
Parent ID |
PARENTID |
Char |
55 |
GF_ParentId |
The Unique ID of the parent record of a subgroup record for ACT! 2000 or later databases only. This field is supplied by the system. |
Parent Name |
— |
Char |
201 |
GVF_ParentName |
The group name of the parent record of a subgroup record for ACT! 2000 or later databases only. This field is retrieved from the Parent ID field and is read-only. |
Priority |
PRIORITY |
Char |
35 |
GF_Priority |
User defined description of the group’s priority. Default selections are High, Medium, and Low. |
Public/Private |
PUB_STATUS |
Num |
5 |
GF_PublicPrivate |
Access level for the group. |
Record Creator |
CREATOR |
Char |
54 |
GF_Creator |
The database user who created the group record. This field is supplied by the system . |
Record Manager |
USER |
Char |
6 |
GF_RecordManager |
The database user permitted to access and change the status of private groups. |
Referred By |
REFER_BY |
Char |
64 |
GF_ReferredBy |
Description of the group’s referral source for ACT! 2000 or later databases only. |
Region |
REGION |
Char |
57 |
GF_Region |
Description of the geographic region of the group for ACT! 2000 or later databases only. |
Revenue |
REVENUE |
Num |
61 |
GF_Revenue |
Revenue for the group for ACT! 2000 or later databases only, stored with 5 digits to the right of the decimal point. |
SIC Code |
SICCODE |
Char |
59 |
GF_SicCode |
SIC (Standard Industrial Classification) code for the group’s industry for ACT! 2000 or later databases only. |
State |
STATE |
Char |
31 |
GF_State |
State in the group’s address. |
Ticker Symbol |
TICKERSYM |
Char |
63 |
GF_TickerSymbol |
Group's stock ticker symbol for ACT! 2000 or later databases only. |
Unique Id |
UNIQUE_ID |
Char |
1 |
GF_UniqueID |
Unique group record identification number. This field is supplied by the system. |
User 1 |
USER1 |
Char |
36 |
GF_User1 |
User-definable field 1. |
User 2 |
USER2 |
Char |
37 |
GF_User2 |
User-definable field 2. |
User 3 |
USER3 |
Char |
38 |
GF_User3 |
User-definable field 3. |
User 4 |
USER4 |
Char |
39 |
GF_User4 |
User-definable field 4. |
User 5 |
USER5 |
Char |
47 |
GF_User5 |
User-definable field 5. |
User 6 |
USER6 |
Char |
48 |
GF_User6 |
User-definable field 6. |
Web Site |
URL |
Char |
65 |
GF_URL |
Group's web site URL address for ACT! 2000 or later databases only. |
Zip |
ZIP |
Char |
32 |
GF_Zip |
ZIP code in the group’s address. |
The following table shows database schema for each field in an ACT! database List table. (Requires ACT! 2000 or later.)
Field name |
Database |
Format/ |
Field |
Field |
Description |
Create
Timestamp |
CTIME |
Char |
2 |
LTF_CreateTime |
Date and time the list record was created. This field is supplied by the system and stored in a compressed format. |
Directory
Name |
DIRNAME |
Char |
26 |
LTF_Name |
Stores a drop-down list entry for a Product, Type or Main Competitor field referenced by a Unique ID in the Sales table. |
Directory
Type |
DIRTYPE |
Num |
25 |
LTF_Type |
Associates
the Directory Name with one of three specific fields referenced by a Unique
ID in the Sales table. |
Edit
Timestamp |
ETIME |
Char |
3 |
LTF_EditTime |
Date and time the list record was last modified. The initial value is the date and time the record was created. This field is supplied by the system and stored in a compressed format. |
Merge
Timestamp |
MTIME |
Char |
4 |
LTF_MergeTime |
Date and time the list record was imported into ACT! or synchronized with another ACT! database. This field is supplied by the system and stored in a compressed format. |
Record
Manager |
USER |
Char |
6 |
LTF_UserId |
Unique ID of the database user who created the list record. This field is supplied by the system. |
Unique
Id |
UNIQUE_ID |
Char |
1 |
LTF_UniqueID |
Unique list record identification number. This field is supplied by the system. |
The following table shows database schema information for each field in an ACT! database Notes/History table.
Field name |
Database |
Format/ |
Field |
Field |
Description |
Attachment |
ATTACHMENT |
Char |
28 |
NHF_Attachment |
The drive, folder, and filename of the attached file. This 6-byte field is supplied by the system and contains a reference to a field in the Binary Large Object Database file that contains a maximum of 256 characters. |
Contact |
CONTACTID |
Char |
29 |
NHF_ContactId |
The Unique ID of the contact record with which the history, notes, or attachment record is associated. This field is supplied by the system. |
Create Timestamp |
CTIME |
Char |
2 |
NHF_CreateTimestamp |
Date and time the history, notes, or attachment record was created. This field is supplied by the system and stored in a compressed format. |
Edit Timestamp |
ETIME |
Char |
3 |
NHF_EditTimestamp |
Date and time the history, notes, or attachment record was last modified. The initial value is the date and time the record was created. This field is supplied by the system and stored in a compressed format. |
Group |
GROUPID |
Char |
30 |
NHF_GroupId |
The Unique ID of any group record with which the history, notes, or attachment record is associated. This field is supplied by the system. |
Merge Timestamp |
MTIME |
Char |
4 |
NHF_MergeTimestamp |
Date and time the history, notes, or attachment record was imported into ACT! or synchronized with another ACT! database. This field is supplied by the system and stored in a compressed format. |
Recorded Date |
— |
Char |
200 |
NHVF_RecordedDate |
The date portion of the User Time field. The format is YYYYMMDD. This field is retrieved from the User Time field and is read-only. |
Recorded Time |
— |
Char |
201 |
NHVF_RecordedTime |
The time portion of the User Time field. The format is HHMM. This field is retrieved from the User Time field and is read-only. |
Regarding |
REGARDING |
Char |
26 |
NHF_Text |
Description of the history event or the attachment, or the text of the note. This 6-byte field is supplied by the system and contains a reference to a field in the Binary Large Object (BLOB) Database file that contains a maximum of 30,000 characters. The next table shows descriptions of the regarding text by type number. |
Type |
TYPE |
Num |
25 |
NHF_Type |
History event, note, or attachment type number. The next table shows values for the type numbers. |
Unique Id |
UNIQUE_ID |
Char |
1 |
NHF_UniqueID |
Unique notes, history, or attachment record identification number. This field is supplied by the system. |
Record Manager |
USER |
Char |
6 |
NHF_UserId |
The Unique ID of the database user permitted to access and change the status of private activities. This field is supplied by the system. |
User Time |
USER_TIME |
Char |
27 |
NHF_UserTime |
Date and time the notes, history, or attachment record was created. The format is YYYYMMDDHHMM. A different date and time can be specified when an activity is cleared to history. |
The following table shows type values and regarding text for the Regarding and Type fields in the Notes/History table.
Type |
Regarding text |
|
Type |
Regarding text |
0 |
Call Attempted |
|
15 |
Delete Activity |
1 |
Call Completed |
|
16 |
E-mail Sent |
2 |
Call Received |
|
17 |
Call Left Message |
3 |
Field Changed |
|
50 |
Fax Sent |
4 |
Access |
|
51 |
Sent Sync |
5 |
Letter Sent |
|
52 |
Received Sync |
6 |
Meeting Held |
|
53 |
Replace Fields Log |
7 |
Meeting Not Held |
|
54 |
To-do Erased |
8 |
To-do Done |
|
55 |
Meeting Erased |
9 |
To-do Not Done |
|
56 |
Error |
10 |
Timer |
|
57 |
Closed/Won Sale (for ACT! 2000 or later) |
11 |
Call Erased |
|
58 |
Lost Sale (for ACT! 2000 or later) |
12 |
Contact Deleted |
|
100 |
Note |
13 |
Update Contact |
|
101 |
Attachment |
14 |
Update Activity |
|
102 |
E-mail (for ACT! 4.0 or later) |
The following table shows database schema for each field in an ACT! database Relational table. All fields in this table are supplied by the system.
Field name |
Database |
Format/ |
Description |
Create Time Stamp |
CTIME |
Char |
Date and time the relational table database record was created. This field is currently blank and reserved for future use. |
Edit Time Stamp |
ETIME |
Char |
Date and time the relational table database record was last modified. This field is currently blank and reserved for future use. |
Field1(ID) |
FIELD1 |
Char |
For type 0 and 1 records, contains the Unique ID of the
record in the contact or group database associated or linked with the group
or activity record Unique ID in Field2(ID). |
Field2(ID) |
FIELD2 |
Char |
Unique ID of the record in the group or activity database that is associated with the contact or group record Unique ID in Field1(ID). |
Field3(Time) |
TIME |
Char |
The activity alarm time. The format is YYYYMMDDHHMM. |
Field4(Time) |
TIME2 |
Char |
The activity scheduled date. The format is YYYYMMDDHHMM. This field is blank if an alarm is not set for the activity. |
Type |
TYPE |
Char |
Database relationship type number. |
The following table shows relationship type values and descriptions in the Relational table.
Type |
Field1(ID) |
Field2(ID) |
Description |
0 |
Contact Unique ID |
Group Unique ID |
Links contact and group database records |
1 |
Contact Unique ID |
Activity Unique ID |
Links contact and activity database records |
3 |
Contact Unique ID of the database user for whom the activity is scheduled |
Activity Unique ID |
Links contact database records with alarms |
The following diagram shows how the Field1(ID) and Field2(ID) fields in the Relational table file are used to link records in the Contact, Group, and Activity table.
The following table shows database schema and Sales tab information for each field in an ACT! database Sales table. The Sales table exists only in ACT! 2000 or later.
Field name |
Database |
Format/ |
Field |
Field |
Description |
Amount |
SAMOUNT |
Num |
34 |
SLF_Amount |
The total amount for the sale, stored with 5 digits to the right of the decimal point. |
Competitors |
— |
Char |
202 |
SLVF_Competitors |
Name of the main competitor for the sale. This field is retrieved from the List table and is read-only. |
Contact |
CONTACTID |
Char |
25 |
SLF_ContactId |
The Unique ID of the contact record with which the sales record is associated. This field is supplied by the system. |
Create Timestamp |
CTIME |
Char |
2 |
SLF_CreateTime |
Date and time the record was created. This field is supplied by the system and stored in a compressed format. |
Creation Date |
STARTDATE |
Char |
35 |
SLF_SaleStartDate |
Date on which the sales forecast was created. The format is YYYYMMDD. |
Details |
NOTES |
Char |
36 |
SLF_Notes |
Description of the sale or sales opportunity. This 6-byte field is supplied by the system and contains a reference to a field in the Binary Large Object (BLOB) Database file that contains a maximum of 32,768 characters. |
Edit Timestamp |
ETIME |
Char |
3 |
SLF_EditTime |
Date and time the record was last modified. The initial value is the date and time the record was created. This field is supplied by the system and stored in a compressed format. |
Forecasted close date |
SDATE |
Char |
31 |
SLF_SaleDate |
Forecasted or actual close date for the sale. The format is YYYYMMDD. |
Group |
GROUPID |
Char |
26 |
SLF_GroupId |
The Unique ID of the group record with which the sales record is associated. This field is supplied by the system. |
Main Competitor |
COMPETID |
Char |
37 |
SLF_CompetitorsId |
The Unique ID of the main competitor for the sale. This field is supplied by the system and references a competitor stored in the List table. |
Merge Timestamp |
MTIME |
Char |
4 |
SLF_MergeTime |
Date and time the record was imported into ACT! or synchronized with another ACT! database. This field is supplied by the system and stored in a compressed format. |
Price |
SPRICE |
Num |
33 |
SLF_UnitPrice |
The price per unit, stored with 5 digits to the right of the decimal point. |
Probability |
PROBABIL |
Num |
30 |
SLF_Probability |
Probability of making the sale as a percentage from 0 to 100. |
Product Id |
PRODID |
Char |
28 |
SLF_ProductId |
The Unique ID for the name of the product. This field is supplied by the system. |
ProductName |
— |
Char |
200 |
SLVF_ProductName |
Name of the product for the sale. This field is retrieved from the List table and is read-only. |
Reason |
REASON |
Char |
38 |
SLF_Reason |
Reason that the sale was closed/won or lost. |
Record Manager |
USER |
Char |
6 |
SLF_UserId |
The Unique ID of the Record Manager for the sale. This field is supplied by the system. |
Sales Stage |
SALESSTAGE |
Char |
39 |
SLF_SalesStage |
Stage of the sale in the sales process (New Opportunity, Pre-Approach, and so on). |
Status |
SLSTATUS |
Num |
27 |
SLF_Status |
Status of the sale. |
Type |
SLTYPE |
Char |
29 |
SLF_TypeId |
The Unique ID of the type for the sale. This field is supplied by the system and references a type stored in the List table. |
TypeName |
— |
Char |
201 |
SLVF_TypeName |
Name of the product type for the sale. This field is retrieved from the List table and is read-only. |
Unique Id |
UNIQUE_ID |
Char |
1 |
SLF_UniqueID |
Unique sales record identification number. This field is supplied by the system. |
Units |
SUNITS |
Num |
32 |
SLF_Units |
Number of units expected to sell or sold. |
The software described in this book is furnished
under a license agreement and may be used only in accordance with the terms of
the agreement.
Copyright Notice
Portions of this publication copyright 2000 Interact Commerce Corporation. Portions of this
publication copyright 1993 ‑ 2000 Symantec Corporation under
exclusive license to Interact Commerce Corporation.
All Rights Reserved.
Released: 6/2000 for ACT! 2000
This document may not, in whole or in part, be
copied, photocopied, reproduced, translated, or reduced to any electronic
medium or machine-readable form without prior consent in writing from Interact
Commerce Corporation, 8800 N. Gainey Center Dr. #200, Scottsdale, AZ 85258.
ALL EXAMPLES WITH NAMES, COMPANY NAMES, OR
COMPANIES THAT APPEAR IN THIS MANUAL ARE IMAGINARY AND DO NOT REFER TO, OR
PORTRAY, IN NAME OR SUBSTANCE, ANY ACTUAL NAMES, COMPANIES, ENTITIES, OR
INSTITUTIONS. ANY RESEMBLANCE TO ANY REAL PERSON, COMPANY, ENTITY, OR
INSTITUTION IS PURELY COINCIDENTAL.
Every effort has been made to ensure the
accuracy of this manual. However, Interact Commerce makes no warranties with
respect to this documentation and disclaims any implied warranties of
merchantability and fitness for a particular purpose. Interact Commerce shall
not be liable for any errors or for incidental or consequential damages in
connection with the furnishing, performance, or use of this manual or the
examples herein. The information in this document is subject to change without
notice.
Trademarks
ACT! is a registered trademark and SideACT! is a
trademark under exclusive license to Interact Commerce Corporation by their
owner, Symantec Corporation, in the United States and other countries. Interact
Commerce Corporation and not Symantec Corporation has produced this publication
and is responsible for the contents hereof. Symantec and WinFax are U.S.
registered trademarks of Symantec Corporation. WinFax PRO is a trademark of
Symantec Corporation. Microsoft, MS, Windows, Windows CE, Windows NT, Word,
Schedule+, ActiveX, FoxPro, Visual Basic, and Visual C++ are either registered
trademarks or trademarks of Microsoft Corporation in the U.S. and/or other
countries. Dale Carnegie Training is a registered trademark of Dale Carnegie
and Associates, Inc. ECCO is a trademark of NetManage Inc. ExpensAble is a
registered trademark of Managemark, Inc. Palm is a trademark of Palm, Inc.
GoldMine is a trademark of Goldmine Software Corp. Janna Contact is the
exclusive property of Janna Systems Inc. Maximizer is a registered trademark of
Modatech Systems Inc. Lotus Organizer is a trademark of Lotus Development
Corporation. Quicken is a registered trademark of Intuit, Inc. Sidekick is a
trademark of Starfish Software. Sharkware is a trademark of CogniTech
Corporation. Tracker is a trademark of Softcode Pty Ltd. Yahoo! is a registered
trademark of Yahoo! Inc. WordPerfect is a registered trademark of Novell, Inc.
CompuServe is a registered trademark of CompuServe, Inc., and its affiliates.
cc:Mail and cc:Mail Mobile are trademarks of cc:Mail, Inc., a wholly owned
subsidiary of Lotus Development Corporation. Day Runner is a registered
trademark of Day Runner, Inc. Day-Timer is a registered trademark of
Day-Timers, Inc. Netscape is a trademark of Netscape Communications
Corporation. Portions of ACT! are Copyright 1995 by Streetwise Software. All
rights reserved.
Other product names mentioned in this
manual may be trademarks or registered trademarks of their respective companies
and are the sole property of their respective manufacturers.
Printed in the United States of America.
10 9 8 7 6 5
4 3 2 1