This document provides information about Maximizer Enterprise 9 Service Pack 1 for Service Release 1 - Series 1618. This service pack contains all fixes from Maximizer Enterprise 9 Hot Fix 2 for Service Release 1 - Series 1609. To view the list of issues addressed in this hot fix, please refer to Hot Fix 2 for Maximizer Enterprise 9 Service Release 1.

• Maximizer Enterprise 9 Hot Fix 2 for Service Release 1 - Series 1609
• Maximizer Enterprise 9 Hot Fix 1 for Service Release 1 - Series 1605
• Maximizer Enterprise 9 Service Release 1 - Series 1552

1. Import Issues with ACT! 2005/2006
   The following issues occurred with an ACT! 2005/2006 import:
   • When notes were imported into Maximizer from ACT!, the date of the note was the date the note was created, not the displayed date from ACT!.
   • Tasks and appointments that were marked as complete in ACT!, were not marked completed in Maximizer after the import.
   • The Ticker Symbol, Last Results, and Phone Label fields were not imported to Maximizer from ACT!.



2. Improved ACT! Import Process for ACT! 2005/2006
   Previously, a direct import of ACT! data was not supported. The Maximizer Import utility has been improved to support the direct import of ACT! 2005/2006 data into an Address Book. The following requirements must be met in order to use this functionality:
   • you must be logged in as a Windows administrator
   • in Maximizer Enterprise, you must be logged in as the Master user
   • the ACT! database (SQL Server instance) must be on the computer where the import is being performed.

   The new improved import process works differently from what is described in the Maximizer Enterprise version 9 Administrator's Guide, although the documented method is also valid. For information on the new process, see the following knowledge base article: How-To: Import ACT! 2005/2006 or ACT! Premium for Workgroups 2005/2006 database



3. X_ Characters Cause Issues with MTI
   User-defined field names preceded by the letter X and an underscore were incorrectly associated with a Contact rather than the Company or Individual when using MTI (Maximizer Transfer Interface) for an import.



4. Out of Memory Message
   Users received an "out of memory" message when using Outlook Express or Outlook as their default email client. The issue occurred when a user attempted to open an email.



5. First and Last Name Order Reversed
   When the default Full Name order was set to "Last, First" in Outlook, first and last names would be reversed after contacts were synchronized from Maximizer.



6. Recurring All-Day/Multiple-day Appointment Transactions
   Recurring all-day or recurring multiple-day appointments created in Outlook and synchronized with Maximizer using Microsoft Outlook Synchronization or MaxSync for Microsoft Exchange caused unnecessary MaxExchange transactions.



7. Location for Appointments Does Not Appear
   When a recurring appointment was created in Maximizer and then synchronized to Outlook, the Location field in the Outlook appointment dialog box was blank. The location appeared correctly in the tooltip when mousing over the appointment and in the calendar views.



8. Outlook Synchronization of Contacts
   When a user had full access rights to a Maximizer Contact through user rights or group rights, but did not have read access rights through a group, the Contact would not synchronize with Outlook.



9. User ID Uniqueness Not Checked
   Maximizer User ID uniqueness was not checked when new users were created and as a result user information could be overwritten.



10. Insert/Update in ODBC UDF_Table_Item Table
    Insertion of records and updates to Name fields were not working properly for the ODBC UDF_Table_Item table (Pervasive databases).



11. Contact/Individual Conversion
    When a Contact with associated records being stored in the Custom_Child table was converted to an Individual, the records in the table were not converted and were deleted. Similarly, the same issue occurred when converting an Individual to a Company or Contact.



12. Default Printer in a Citrix Environment
    Under certain circumstances in a Citrix operating environment, the default printer for Maximizer was incorrect.



13. Opportunity Fields Now Full Access
    The Opportunity.Cont_Client_Id and Opportunity.Cont_Cont_Number fields were read-only. This was an ODBC driver issue. The fields can now be inserted and updated.