|
|
 |
| Maximizer > Support > Answers to Your Questions - Maximizer Enterprise Product History |
| |
Maximizer Enterprise 8 Hot Fix No. 2 - Series 1420
Released on May 20th, 2004
|
| |
| Type of Release: |
Hot Fix Release |
| PSN Prefix: |
N/A |
| Files Modified: |
distlist.exe; LicenseApp.dll; MaAccess.dll; Madata6.dat; MaDIV.dll; MaMaster.dll; Maxdbase.dll; Maxexsql.dll; MaxWord.ter; MxMail97.dll; Spdm.exe |
|
| |
| Changes: |
- Global Edit of Mandatory, Single-Value User-Defined Fields: When global edit was used to modify a mandatory, single-value user-defined field, the single-value rule was not enforced.
- Global Edit of Address Book Entry Ownership: When Address Book entry ownership was changed to Public from a security group or user through global edit, the entries were visible only to the MASTER user or users with the "Modify other users' private entries" security privilege.
- Global Edit Clearing Mandatory User-Defined Fields Values: When performing a global edit with the Global Edit Rules set to "Replace table field values", mandatory fields that had been assigned to the associated Address Book entry were cleared.
- License Count Incorrectly Set to Zero: If users opened an Address Book in Administrator from a workstation other than the one on which the Maximizer Enterprise licenses were installed, the license count was reset to 0 for that Address Book.
- MaxExchange License Count Incorrectly Set to Zero: If users opened an Address Book on a workstation where MaxExchange was not installed, the MaxExchange license count was set to 0.
- User-Defined Field Order Synchronization: When you changed the order of a user-defined field in the user-defined field list on a MaxExchange Server and synchronized to your remotes, the order was not changed on the remotes.
- User-Defined Field Layout Structure Synchronization: When you added new user-defined field folders and added user-defined fields to these folders later, the user-defined fields did not synchronize correctly.
- Inserted Objects in the Maximizer Word Processor: Objects inserted into a Maximizer Word Processor document or template could not be seen when the document or template was opened for editing.
- Data Manager Error Code 81: AA Data Manager error code 81: "A LOCK Error occurred on the 'Documents and Templates' file" could occur in the Documents window.
- OLE Error 16389 - Inserting Objects in Documents Window: An error occurs when attempting to insert an object in a document in the Documents window. This issue is resolved by applying the Pervasive.SQL V8 SP1 Hot Fixes, available from Pervasive Software Inc. The filenames for these Hot Fixes are HF_MKDE.EXE and HK_SRDE.EXE, and you can download them from http://www.pervasive.com/support/updates/v8_hotfix.asp. For more information, refer to Maximizer Technical Bulletin 20040520-178.
- Complete Body of Some HTML Messages Not Visible in Maximizer Email Message Windows: When viewing HTML email messages in Maximizer, some sections of the HTML messages would be omitted.
|
  |
| |
Maximizer Enterprise 8 Hot Fix No. 1 - Series 1409
Released on February 27th, 2004
|
| |
| Type of Release: |
Hot Fix Release |
| PSN Prefix: |
N/A |
| Files Modified: |
distlist.exe; Madata6.dat; MaDIV.dll; MaMaster.dll; Maxdbase.dll; Maxexsql.dll; MxMail97.dll; Spdm.exe |
|
| |
| Changes: |
- Incorrect Address Book Entries Sent in Refresh: Address Book entries associated with remotes were not sent properly when a refresh was sent from the server after the MaxExchange server was upgraded to version 8 from version 7.5. The cause of the issue was related to the server incorrectly determining that the remotes had been upgraded to version 8; the remotes had not yet been upgraded.
- Missing Email Addresses for Remotes for Pervasive Users: For Pervasive users only, email addresses were missing for MaxExchange remotes using the email transport method after the server was upgraded to version 8.
- Incorrect Distribution Assignment for Remotes: An issue with MaxExchange remote distribution assignment occurred after upgrading a Pervasive Address Book to a SQL Address Book. In addition to fixing the issue in this hot fix, an item called Import Pervasive Distribution Groups has been added to the File menu in MaxExchange Site Manager to allow the administrator to retrieve the distribution assignment from the original Pervasive file.
- Error Code 51 Messages on Remotes: When launching a MaxExchange remote after upgrading to version 8, the remote receives Error Code 51 messages. This issue was related to the synchronized Address Book not yet being upgraded on the remote.
- MaxExchange Site Manager and Server Manager Start-Up: MaxExchange Site Manager and MaxExchange Server Manager would start and then exit when an Address Book was upgraded from Pervasive to SQL. This issue was related to data not being properly converted.
- Remote Users Prompted for MASTER's Password: MaxExchange remote users were prompted for the MASTER's password when attempting to upgrade an Address Book.
- Incorrect Search Results in Pervasive Address Book: Search by City/Town, State/County/Province, Zip/Postcode, and All Phone Numbers did not return the correct results in a Pervasive Address Book.
- Multiple Draft Email Incorrectly Appearing in Outbox: Multiple draft versions of an email appeared in the Outlook Outbox. In order for this to occur, the email must have been created using Maximizer's Compose Email dialog box, with the "AutoSave unsent email every "x" minutes in Inbox" option selected in Maximizer Email preferences.
- MaxExchange Remote Server & Remotes Connected to Server: MaxExchange remote servers and the associated remotes were incorrectly connected to the parent server after an Address Book was upgraded from Pervasive to SQL.
- Distribution Lists Not Rebuilt for Pervasive Users: Remote sites may have experienced problems with their distribution lists (DRB files) not being rebuilt when Address Book Maintenance was performed at the server. This hot fix addresses this problem, however, Address Book Maintenance should be performed after installing the hot fix to rebuild the distribution list. When Address Book Maintenance is performed, you must select the "Right Now" and "Do Not Create Maintenance Data Packets" options.
|
| |
|
| |
|
|
|
|
 |
