|
|
 |
| Maximizer > Support > Answers to Your Questions - MaxExchange Product History |
| |
MaxExchange Synchronization Server 9 Service Pack 1 for Service Release 2 – 1649
Released December 11, 2006
|
| |
| Type of Release: |
Service Pack |
| PSN Prefix: |
N/A |
| Files Modified: |
Spdm.exe; Meclient.exe; distlist.exe |
|
| |
Issues Resolved by Service Pack 1:
- Column Setup Settings Not Synchronizing Properly
When a user selected certain column setups on a Pervasive.SQL database and then synchronized to a Microsoft SQL database, some Maximizer windows may not have opened in the Microsoft SQL database. In addition, some user drop-down lists may have appeared incomplete.
- Favorite List Settings Not Synchronizing Properly
When a user specified certain Favorite Lists on a Pervasive.SQL database to be retrieved in the Address Book window or the Customer Service window upon startup of Maximizer, and then synchronized the settings to a SQL database, Maximizer may have closed unexpectedly.
- Opportunities Not Synchronizing Properly
This issue occurred when the remote was not upgraded to Maximizer Enterprise 9 Service Release 2 - Series 1635. Under certain circumstances, when a user added a new
opportunity on a MaxExchange Remote running a Pervasive.SQL database and modified the selected team, the opportunity may not have synchronized properly to a MaxExchange Server running a Microsoft SQL database.
|
| |
  |
| |
MaxExchange Synchronization Server 9 Service Release 2 - Series 1635
Released on October 8th, 2006
|
| |
| Type of Release: |
Service Release |
| PSN Prefix: |
N/A |
| Files Modified: |
Spdm.exe; Melib.dll; Maxexsql.dll; distlist.exe; Meclient.exe; AboutMaximizer.dll; MaxExchEvents.exe |
|
| |
Issues Resolved by Service Release 2:
- Key Value Generation Problem
An issue may result regarding key value generation when creating new Distribution Sites and Teams from MaxExchange Site Manager. These entries may not be saved to the SQL database. In addition, some types of entries such as Favorite Lists, Column Setups, and Strategies may not be
synchronized properly from a Pervasive database to a SQL database.
- Simultaneously Modified Notes and Documents Not Updated
Simultaneously modified notes and documents on remotes and servers may not have been updated properly after synchronization.
- MaxExchange Server Closes After Delete
Under certain circumstances, MaxExchange Server would close
after an Address Book entry was deleted on a remote
and synchronized to the server.
- OrderDesk Fields Removed from Remote
Under certain circumstances, modified OrderDesk fields on a
remote were removed after processing the next packet from
the server.
- Related Entries Not Synchronized
If an Address Book entry had more than one related entry,
only one entry would appear in the Related Entries tab after
sending a refresh to a remote.
- Global Edit Changes Not Synchronized Properly
When using global edit on a remote to make changes to
mandatory table user-defined field items using the
"Replace table field values" rule, values for these fields
were not synchronized to the server properly; both the new
value and the old value appeared in the field.
- Opportunity Document Cannot be Opened
When an opportunity had a large document and a refresh was
sent to a remote, the file could not be opened on the
remote.
|
| |
|
| |
|
|
|
|
 |
