INFO:  

APPLIES TO

Resolved
* UpdateToSuperOffice: 5 Invalid procedure call or argument.
* Duplication of the subject text within an Outlook appointment.

Note on building the subject and location field:
When the following options are set in the SynchronizerAdmin, in the panel ‘SuperOffice SIX Settings’
External Subject Line: <250 characters of App. Or Task Text>
You have the following behavior
Situation 1:
- When the appointment is originally created in SuperOffice, only the first 250 characters of the appointment text will be placed in the subject field in Outlook. The complete appointment text will be placed in the body field of the Outlook appointment.
- When this appointment is changed in Outlook, meaning a new subject line and or location is filled in, this will be overwritten by the Synchronizer with the first 250 characters of the appointment text.
Situation 2:
- When the appointment is originally created in Outlook, the Synchronizer will respect the subject and or location field of Outlook in the SuperOffice appointment text.
- When this appointment is changed in Outlook, meaning a new subject line and or location is filled in, this will be not overwritten by the Synchronizer with the first 250 characters of the appointment text.

When the following options are set in the SynchronizerAdmin, in the panel ‘SuperOffice SIX Settings’
External Subject Line: <Task Type><First line of App. or Task>
You have the following behavior
Situation 1:
* When the appointment is originally created in SuperOffice, only the first line of the appointment text will be placed in the subject field in Outlook. First line is recognized by the first carriage return found. The complete appointment text will be placed in the body field of the Outlook appointment.
* When this appointment is changed in Outlook, meaning a new subject line and or location is filled in, this will be overwritten by the Synchronizer with the first line of the appointment text.
Situation 2:
* When the appointment is originally created in Outlook, the Synchronizer will respect the subject and or location field of Outlook in the SuperOffice appointment text.
* When this appointment is changed in Outlook, meaning a new subject line and or location is filled in, this will be not overwritten by the Synchronizer with the first line of the appointment text.

Remark: You can easily determine where the appointment is created by looking at the SuperOffice appointment text, if the appointments text has the fields: Subject: Location: and -------------, this means the appointment was originally created in Outlook.

InfoBridge Version 3.0.4/SuperOffice Version 1.2.10

Resolved
* When the date separator character contained an invalid character creating of the user statistics file would fail.
* When the Outlook body of an appointment is larger then 2000 characters, the Synchronizer will not update the body text (in Outlook) from SuperOffice to Outlook.

Synchronizer
* Vista Compatible
* When the SuperOffice appointment has no related company, the Outlook subject will hold the SuperOffice task type.
* Colors which are set in Outlook 2007, will be maintained, even when the color scheme in SuperOffice is not used.
* Phone Numbers are also synchronized to the body of the Outlook appointment, which will give quick dial access from mobile phones

SynchronizerAdmin
* Option added to reset the users, so that the synchronization will perform a fresh start, missing appointments will be added if necessary. It will not create duplicates!
* Purify phone number option added, so that the phone which is been synchronized to the appointment/task text, does not contain any invalid characters
* New option added for building Outlook appointments, <task type>: <First line of the appointment text> First line is determined by the first carriage return found.
* Notifier option to get instantly notified by mail of changes in the diary
* Option added to NOT synchronizer the alarm set in SuperOffice to Outlook
* Option added to NOT synchronizer the alarm set in Outlook to SuperOffice
* From now on, the SynchronizerAdmin is always in English.
* Option added to select all activity types, instead of selecting the activities one by one

Note
* Time Zone support from SuperOffice is not supported in Outlook 2007, however the Time Zone support of Outlook 2007 is supported in SuperOffice, this is due the incompatibility between the Time Zone setup of SuperOffice and the Microsoft platform.

InfoBridge Version 3.0.3/SuperOffice Version 1.2.9
* Internal Changes

InfoBridge Version 3.0.2/SuperOffice Version 1.2.8
* Internal Changes

InfoBridge Version 3.0.1/SuperOffice Version 1.2.7
* Keycode handling for both versions added

InfoBridge Version 3.0.0/SuperOffice Version 1.2.6

Synchronizer
* In some cases Runtime Error 6 Overflow occured and the sync would not continue with adding appointments, this issue was   caused when the group_idx of an appointment record   would not fit in a integer variable.
* Synchronizer.exe now checks at startup of redemption.dll is available, when redemption.dll is missing, linking of users   would work in SynchronizerAdmin,
  but when the Synchronizer would access the folders, the message appeared Problem getting folder xx
* userid and password are not converted anymore to uppercase, this could cause problems on SQL server 2005
* Synchronizing resources will work now

SynchronizerAdmin
* When linking a resource as a syncuser, an error would occur.
* It is possible now to link resources as a syncusers
* The list of resources also contained deleted resources
* Linking of a mailbox name with a ' in the name would fail
* userid and password are not converted anymore to uppercase, this could cause problems on SQL server 2005
* Better description for US and Dutch language for the options Enable simple logand Enable debug
* The option DELETESYNCTABLES is now also removing the userpreference settings of the synchronizer
* The option DELETESYNCTABLES will continue deleting tables even when the first table is already deleted

InfoBridge Version 3.0.0/SuperOffice Version 1.2.5

Synchronizer
* Encryptedcheck field is now filled with a ' ' blanc character, this bug caused the following behaviour:
  - Appointment would be added to SuperOffice
  - Insert in the visiblefor table would fail because blanc character was not allowed
  - Because of this error the record was not added in the Synchronizer History table
  - In next run the same appointment is not found in the Synchronizer history table, so the record would be added again to     SuperOffice

SynchronizerAdmin
* There is an issue with the SDKDictonary on Oracle, when there is not enough space (SYSTEM) or rights, the first table (syncuser) will be created in the Oracle database, however the
  remaining tables will not be created.
  Extra checked is build in, to see if also the last table exists (synctemp) in the SuperOffice database, if this is not the case the user will get the following errormessage:
  "Not all Synchronizer tables are found, some tables are missing. Please start the SynchronizerAdmin with the parameter DELETESYNCTABLES and try to create the tables again. Make sure the user has sufficient rights in 'Oracle' to create tables!"

  This would cause the following issue;
  - It seams everything is working, the synchronizeradmin works completely, however the Synchronizer will not find the remaining tables and will display an error.

InfoBridge Version 3.0.0/SuperOffice Version 1.2.4

Synchronizer
* When linking a user in SynchronizerAdmin on Oracle 10g, the emailaddress which should be empty will containt one space, this would mean
  the emailaddress is not empty, so the synchronizer will try to resolve the exchange user based on the blank emailaddress instead of the unique
  exchange id. This would cause the following problem;
  - Link the user in SynchronizerAdmin
  - Start the synchronizer, message would appear: can not resolve user

SynchronizerAdmin
* No Change, just version number update to keep versions in sync

InfoBridge Version 3.0.0/SuperOffice Version 1.2.3

Synchronizer
* Bug fixed when the Outlook Subject or location would exceed 250 characters, this bug caused the following problem;
  - Appointment would be added to SuperOffice
  - Appointment could not be stored in the Synchronizer History table
  - In next run the same appointment is not found in the Synchronizer history table, so the record would be added again to SuperOffice
  - Again this new added appointment could not be added to the Synchronizer History table
  - This would happen each time when the synchronizer would run.
  - The end result is that many duplicate appointments would be created on the same day

* In the Outlook mode (personal edition) the settings made in the SynchronizerAdmin where not read on startup of the Synchronizer,
  this bug caused the following behaviour:
  - Setting made for example start minimized, and sync every minute
  - The synchronizer would start, but the user had to press the start button, because there settings for the user where not read at startup

SynchronizerAdmin
-----------------
* No Change, just version number update to keep versions in sync

InfoBridge Version 3.0.0/SuperOffice Version 1.2.2

Synchronizer
* Added support for handling internal sybase travel, in case when a internal sybase travel database gets detected it uses the following
connectionstring:
dDatabase.ConnectionString = "Driver=SuperOfficeTravel;Start=" & SODB.Settings.ProgPath + "\Database\dbeng9.exe -q -c 8m;Integrated=No;DatabaseFile=" & SODB.Settings.LocalArchivePath + "\Data\SuperOfficeTravel.db;UID=" & sUserID & ";PWD=" & sPassWord

SynchronizerAdmin
* When running the SynchronizerAdmin in the Exchange mode (/E) the option Restart every # minute could not be checked,
  a message would popup telling the watchowl should be enabled, even if the watchowl was enabled

InfoBridge Version 3.0.0/SuperOffice Version 1.2.1

Synchronizer
* Release

SynchronizerAdmin
* Release