Internal Error
File:../libdbapi/odbc2.c
Line:610
In Fcn.:sql_exec_direct
Called Fcn.:SQLExecDirect() returned -1
Description:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

SQL Error SQL Error
File:../libapi/stats.c
Line:79
In Fcn.:stats_increment
SQL Fcn.:sql_exec_direct() returned -1
SQL Stmt.:INSERT INTO stats (stat_date, hits, searches, assists, email_assists, smarts, sessions, ans_viewed, interface_id) VALUES ('2010-09-07 00:00:00', 0, 0, 0, 0, 0, 1, 0, 1)
SQL Error:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

Internal Error Internal Error
File:../libdbapi/odbc2.c
Line:610
In Fcn.:sql_exec_direct
Called Fcn.:SQLExecDirect() returned -1
Description:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

SQL Error SQL Error
File:../libapi/stats.c
Line:79
In Fcn.:stats_increment
SQL Fcn.:sql_exec_direct() returned -1
SQL Stmt.:INSERT INTO stats (stat_date, hits, searches, assists, email_assists, smarts, sessions, ans_viewed, interface_id) VALUES ('2010-09-07 00:00:00', 1, 0, 0, 0, 0, 0, 1, 1)
SQL Error:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

Internal Error Internal Error
File:../libdbapi/odbc2.c
Line:610
In Fcn.:sql_exec_direct
Called Fcn.:SQLExecDirect() returned -1
Description:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

SQL Error SQL Error
File:../libapi/stats.c
Line:189
In Fcn.:stats_update_faq
SQL Fcn.:sql_exec_direct() returned -1
SQL Stmt.:INSERT INTO incident_stats (ref_no, faq_date, faq_hits, interface_id) VALUES ('030304-000002', '2010-09-07 00:00:00', 1, 1)
SQL Error:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

Internal Error Internal Error
File:../libdbapi/odbc2.c
Line:610
In Fcn.:sql_exec_direct
Called Fcn.:SQLExecDirect() returned -1
Description:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

SQL Error SQL Error
File:solved.c
Line:68
In Fcn.:solved_increment
SQL Fcn.:sql_exec_direct() returned -1
SQL Stmt.:UPDATE incidents SET solved_count = solved_count + 2, access_time = '2010-09-07 11:30:03' WHERE ref_no = '030304-000002'
SQL Error:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

Internal Error Internal Error
File:../libdbapi/odbc2.c
Line:573
In Fcn.:sql_execute
Called Fcn.:SQLExecute() returned -1
Description:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

Answer
 
Maximizer > Support > Knowledge Base Search New - Searching Tips Disclaimer
 Answers 
   
  Help  
Search Results
Related Answers
Product

   
Category

     
Search Text (optional) Search Tips? 
   
Search by      Sort by

Powered by RightNow Web
  Reference #  
030304-000002
  Product  
Maximizer
  All Articles
  Category  
How-To
  Import - Export
  Date Updated  
10/21/2009 04:02 PM

 Print  Print Answer 		  
  ACT! 2000 (5.0), 6.0, 2004, 2005, or 2006 import field mapping
  Question
  This article provides information about how fields are mapped during a Maximizer import from ACT! 2000 (5.0), 6.0, 2004, 2005, or 2006.

Note: Data must be exported from ACT! to a DBF file before importing into Maximizer. The DBF file should be used for the Maximizer import.

  Answer
  ACT! Import Mapping When importing data into Maximizer from ACT!, fields are mapped as described in the following table:
ACT! 2000 (5.0), 6.0, 2004, 2005, or 2006 Maximizer Imported? Comments
Company Company Yes  
Contact First Name & Last Name Yes ACT! Contacts are imported as Contacts in Maximizer and the basic information about each Contact such as email address are imported into the Basic Info tab in the Address Book entry dialog box. If any of the information associated with the Contact cannot be mapped to a Maximizer field in this tab, the information is imported as user-defined fields. In ACT!, First and Last Name belong to the same single field. The correct names may not be properly imported into Maximizer. For example, a Contact 'Toni Spooner (female)' in ACT! is imported into Maximizer as "Toni Spooner" in the First Name field and "(female)" is the Last Name field.
Title Position Yes  
Department Department,
Position		 Yes In Maximizer, Department is populated with the Department information of the first contact and the rest in the Position field separated by comma.
Phone Phone 1 Yes  
Fax Phone 2 Yes Adds FAX to Extension field in Maximizer
Mobile Phone 4 Yes Adds CELL to Extension field in Maximizer
Alt Phone   No  
Ticker UDF Ticker
Symbol		 Yes Adds UDF to Company
ID/Status UDF ID/Status Yes Adds UDF to Company
Address Address Yes First address line in Act! is imported as Address 1 in Maximizer. Second line goes to Address 2. Address comes from one of the contacts for this company and if there is no address, it may end up empty. Alternate addresses are added to Maximizer from different Contacts of the company and alternate addresses are named by that contact. The same address is not added but renamed by the other Contact. For some contacts, the appropriate alternate address may not be selected.
Address Division   Division in Maximizer may be populated by the address line in ACT!.
City City/Town Yes Imported correctly to main and alternate addresses.
State St/Co/Prov Yes Imported correctly to main and alternate addresses.
Zip Zip/Postcode Yes Imported correctly to main and alternate addresses.
Country Country Yes Imported correctly to main and alternate addresses.
Referred By UDF Referred By Yes Adds UDF to Company
Web Site Website Yes Imported into the Company’s website field
E-mail Address Email Yes Imported into the Contact's email field.
Last Result Creates Table UDF
named "Result"		 Yes Adds Company Table UDF with corresponding items selected for each contact.
Assistant   No  
Asst. Title   No  
Asst. Phone   No  
User fields for Contacts and Companies(ACT! 2005/2006 & ACT! 2005/2006 Premium only) Creates UDFs for contracts and Companies with the same name as in the source database Yes Any fields that are of MEMO type or are more than 120 characters are converted to Notes in Maximizer
User 1...
User 15		 Creates UDFs named
"Details Field 1" to
"Details Field 15"		 Yes Adds UDFs to Company and some UDFs that belong to some different contacts in ACT! may be lost.
Users Users Yes ACT! users are imported into Maximizer as users. Passwords are set to "maximizer" if the import was done using a DBF file. Users are displayed in the Administrator's Users dialog box which may be accessed by choosing File > Users. If a user name contains spaces, the spaces are replaced with underscores, and the user names are shortened to 9 characters if necessary. In the SQL version of Maximizer, password synchronization from Utilities > System Configurations menu is necessary before any imported user is able to log into Maximizer. Passwords are then set to "maximizer". In the Pervasive version, passwords have to be set manually for each imported user.
Notes Notes Yes  
Schedule Call
Schedule To-do		 Hotlist Task Yes The Duration information of a task in
ACT! is imported as "Prior to task" in
Maximizer.The company name of some
conflicting tasks may not be preserved.
Schedule Meeting Appointments Yes Recurring appointments
are not imported.
Notes
Attachments		 Notes
Attachments		 No  
Document Document No  
Groups Groups No  
Home Address Address No  
Sales/
Opportunities		 Opportunities No  
History (ACT! 2005/2006 & ACT! 2005/2006 Premium only) Notes Yes Each entry from the History tab in ACT! becomes a Note in Maximizer.


APPLIES TO

• Maximizer 9
• Maximizer Enterprise 9
• Maximizer Enterprise 9.5


At 10/21/2009 04:02 PM we wrote - Removed a line.
 
  How well did this answer your question?
 
100% 0%   
Back
  Back to Search Results