============================================================================
This file contains the list of the correctives 
made to OroTimesheet 6

OroLogic Inc., January 8, 2010
============================================================================

============================================================================
************************ Version 6.14 (January 8, 2010)
============================================================================
Database structure:
==================
Modified (See note at the end of this document)


Correctives:
============
Fixed a problem in the punch clock program. It could happend that it was not 
the time of the server that was saved into the database when the employee 
punched in or punched out.


Improvements:
=============
It is now possible to indicate a maximum number of time units per day 
per employee.


============================================================================
************************ Version 6.13 (October 28, 2009)
============================================================================
Database structure:
==================
Modified (See note at the end of this document)


Correctives:
============
Fixed a problem in sub-projects. In some cases, expense total displayed in
a sub-project did not match the reality.

Fixed some reports. Refer to the FAQ# 10136-EN of OroTimesheet 6 in the
"Support" section of our web site.


Improvements:
=============
Some keyboard shortcuts were added when entering timesheets. Refer to the 
OroTimesheet 6 user's guide for the keyboard shortcut list.


============================================================================
************************ Version 6.12 (September 11, 2009)
============================================================================
Database structure:
==================
Not modified (See note at the end of this document)


Correctives:
============
Fixed a problem when modyfying timesheets via the week view. In some rare 
cases and according to specific situations, it could happend that a 
timesheet be saved over another existing timesheet. 

Fixed other minor problems.


============================================================================
************************ Version 6.11 (August 3, 2009)
============================================================================
Database structure:
==================
Not modified (See note at the end of this document)


Correctives:
============
Fixed a problem in the "Import" option.

Fixed a problem in the punch clock program.


============================================================================
************************ Version 6.09 (June 1, 2009)
============================================================================
Database structure:
==================
Not modified (See note at the end of this document)


Correctives:
============
Fixed a display problem when entering timesheets through the week view.

Fixed a display problem in the web interface when the Firefox browser was
used.

Fixed other minor problems.


============================================================================
************************ Version 6.08 (April 29, 2009)
============================================================================
Database structure:
==================
Modified (See note at the end of this document)


Correctives:
============
Fixed a problem with report search criteria. In some cases, when search 
criteria were modified, the report was not refreshed.

Fixed some reports. Refer to the FAQ# 10127-EN of OroTimesheet 6 in the
"Support" section of our web site.

Fixed a problem when calculating time banks. An erroneous value was written
in the history. The history will be automatically corrected when you will 
install the update 6.08 or higher.


============================================================================
************************ Version 6.07 (March 19, 2009)
============================================================================
Database structure:
==================
Not modified (See note at the end of this document)


Correctives:
============
Fixed a problem with reports. Some RAP functions worked only in the reports
generator and did not work via OroTimesheet.

Fixed a problem with criteria selection when running reports.

Fixed other minor problems.


============================================================================
************************ Version 6.06 (February 17, 2009)
============================================================================
Database structure:
==================
Not modified (See note at the end of this document)


Correctives:
============
Fixed a problem with the option Timesheet batch modification. In some cases 
and according to options selected (option "Billing and cost 
 - Use current rates"), begining and ending dates entered did not correspond 
to dates of timesheets updated.

Fixed display problems.


Improvements:
=============
It is now possible to enter a timesheet with zero time unit if the timesheet
contains at least one expense.

Added three new supervision rights for the employee record:
  The first one named "Can add employees to this group" allows an employee 
  that does not have administrator rights to add an employee in the 
  supervised group.

  The two other ones named "Can see billing rate" and "Can edit billing rate"
  allow to see or to modify the billing rate in the record of the supervised 
  employee.


============================================================================
************************ Version 6.05 (January 12, 2009)
============================================================================
Database structure:
==================
Not modified (See note at the end of this document)


Correctives:
============
Fixed a problem with the option that convert punch clock transactions into
timesheets. In some cases, the option could generate timesheets with an 
abnormally elevated number of hours.

Fixed a problem in the installation program. When installing in stand alone 
mode, some files were missing and could prevent OroTimesheet to correctly
run. See FAQ# 10126-EN in the support section for more information.

Fixed a problem in the OroTimesheet 5 to OroTimesheet 6 data transfer program.
In some cases, the transfer program could not connect to the OroTimesheet 6 
database and displayed the following error message: 
"unsupported on-disk structure".

Fixed a problem with memory management.

Fixed other minor problems.


Improvements:
=============
If the connection with the database is temporarily lost (for example because
somebody is rebooting the server), the punch clock software will now be able
to reconnect itself to the database without having to restart the program 
manually. This applies to the Timer for OroTimesheet program also.

When entering timesheets via the weekly view (Windows version) or via the Web 
version, projects/activities entered in the previous week are automatically 
displayed in the current week with values to 0. It is now possible to disable 
this feature.

When adding new timesheets via the Web version, the new timesheet is now 
displayed at the beginning of the page instead of at the bottom of the page.


============================================================================
************************ Version 6.04 (December 8, 2008)
============================================================================
Database structure:
==================
Not modified (See note at the end of this document)


Correctives:
============
Fixed a problem in the punch clock software. The punch clock stopped
working after some hours.

Fixed a problem with memory management.

Fixed a problem with the option Synchronization.


============================================================================
************************ Version 6.03 (November 26, 2008)
============================================================================
Database structure:
==================
Not modified (See note at the end of this document)


Correctives:
============
Fixed display problems.

Fixed other minor problems.


Improvements:
=============
Web version: There is now two separate drop down lists to select project
and sub-project instead of only one.


============================================================================
************************ Version 6.02 (November 12, 2008)
============================================================================
New major version.

============================================================================
************************ Version 6.01
============================================================================
BETA versions only


============================================================================
End of the list of correctives
============================================================================




============================================================================
************************ Notes
============================================================================

Database structure "Modified":
==============================
Indicates that this update must update the database structure. When the first user access the 
database using the new updated version, a confirmation message is displayed to modify the 
database structure. If the user answer "Yes" to the confirmation message, the database is 
automatically modified (Note that only users with Administrator rights are allowed to modify 
the database structure). Once the database structure is modified, users of earlier
versions will not be able to access the database anymore. You will have to install the new 
update on each computer and/or server so that all users can access the database again. 
When an update must modify the database structure, it is recommended to plan the deployment 
of the new update on each computer and/or servers.


Database structure "Not Modified":
===============================================
Indicates that this update does not have to modify the database structure. So, it is not 
necessary (although recommended) to install the new update on all computers and/or servers. 
Users of earlier versions will be able to continue to access the database.

============================================================================