• Updated Pervasive.SQL v8.6 Engine: The new Pervasive.SQL v8.6 is included in the full installation of Maximizer Enterprise 8 Service Release 2. The new engine helps address the OLE issues and the catalog searches issue outlined below.

  • OLE Error when opening documents: An OLE error 65535 occurred when a user tried to open entries that contained embedded objects from the Documents window. Pervasive.SQL v8.6 resolves this issue.

  • OLE error when opening documents after a transfer: An OLE error occurred when a user tried opening Documents created from a file after completing a transfer. Pervasive.SQL v8.6 resolves this issue.

  • Catalog searches not available: Any attempt to save or retrieve a catalog search failed, when the Address Book was not local. Pervasive.SQL v8.6 resolves this issue.

• Slow performance when opening a large Address Book: Slow performance occurred when opening a large Address Book that contains a large number of table user-defined fields while viewing some of them in the Column Setup view.

• VIM Improvements - A number of issues that appear when using VIM as the email system have been addressed as follows:

  • The action of retrieving the list of email messages was very slow when a user refreshed or pressed the Deliver Now button.

  • When a user tried to reply to an email from Maximizer, the reply email would not display the sender's email address properly.

  • If a user replied to a saved email, the text "<>" would get added to the recipient's email address causing the message not to be sent properly.

  • The Address Book entry column in the Email window did not show the corresponding Address Book entry.

  • When an email message was dragged and dropped to the Address Book window and the email address of the target Address Book entry was updated or a new Address Book entry was created, the email address was entered incorrectly as the Address Book entry's name in addition to the entry's email address.

  • If a user tried to delete email messages from the Maximizer Email window, email messages were removed from the list, but not actually deleted. The messages would reappear when a refresh was performed.

• Unable to open or compose email messages using the email provider's editor: When the Maximizer to Outlook Calendar Integration was used with the email features in Maximizer; a user was not able to open or compose messages using the email provider's dialog boxes. The Outlook.exe file stayed in memory causing issues opening and composing messages using the email provider's dialog boxes.

• Printing an email to a file caused Maximizer to hang: If a user tried to print an email to a file from the Maximizer Email dialog box, Maximizer would stop responding.

• Maximizer would stop responding if using Outlook Express: If Outlook Express was installed as the only email client and an email document was assigned to an Address Book entry with an attachment, opening the document and double-clicking on the attachment caused Maximizer to stop responding.

• Opening a table user-defined field: Opening a table user-defined field containing a large number of items in the User-Defined Fields following window caused Maximizer to stop responding.

• Calendar refresh problem in the weekly calendar view: If a user invoked a view of a future week using the weekly calendar view, and then switched to another window and then back to the weekly calendar view, appointments that were previously visible no longer appeared in the weekly calendar view. The issue occurred when the Calendar window was maximized and when non-working days were not shown.

• Appointment conflicts with free-form location: When creating an appointment with a free-form location, a conflict was reported when a user tried to save the appointment even though there were no appointments booked with that same free-form location.

• Large fonts in calendar causing exception: When using extra large fonts on Windows XP, attempting to open the calendar would cause the error "Exception: displayapp3".

• Graphing By State/Province not working: When graphing by State/Province, no graph was generated.

• Unable to run Crystal Reports if the Address Book was password protected in Pervasive: If using Pervasive, Crystal Reports could not be run if an Address Book was password protected. An Error 51- invalid owner name would appear.

Portals:

• Incorrect dialog box appearing in the Employee Portal: After pressing the Cancel button in the Address Book dialog box when adding a contact, opening the Address Book entry dialog box resulted in the Add Contact dialog box being invoked.

• Close Date Field: The Close Date field was not being saved correctly when closing an Opportunity (giving it a status of Won, Lost, Abandoned, or Suspended) in Employee Portal or Partner Portal.

Notes:

• PDF files are now printable: The Maximizer Enterprise 8 User's Guide, Maximizer Enterprise 8 SQL Administrator's Guide, Maximizer Enterprise 8 Pervasive Administrator's Guide, and Customization Suite Guides are now printable.

• Service Release 2 includes Pervasive.SQL v8.6: The new Pervasive.SQL v8.6 database engine is included in Maximizer Enterprise 8 Service Release 2. The new engine helps address the OLE issues and the catalog searches issue outlined above.

• Service Release 2 Includes All Service Release 1 and Hot Fix 1 and 2 Fixes: Maximizer Enterprise 8 Service Release 2 includes the fixes for all issues resolved in Service Release 1 - Series 1425, Hot Fix 1 - Series 1409, and Hot Fix 2 - Series 1420.

• Running Service Release 2 in Mixed Modes: Maximizer Enterprise 8 Service Release 2 has no database changes and can be used safely in a mixed mode of servers and workstations, as well as MaxExchange Synchronization remote servers and remote workstations, running a combination of the original Maximizer Enterprise 8 release, Maximizer Enterprise 8 Service Release 1, and Maximizer Enterprise 8 Service Release 2.

• MaxExchange Synchronization Server Updates: This release applies to Maximizer Enterprise and MaxExchange Remote only. Install MaxExchange Server 8 Service Release 2 for updates to MaxExchange Synchronization Server and MaxExchange Remote Synchronization Server.