Timesheets Lite: March 2012 Archives

As I am writing this Timesheets Lite version 3.1.0 is being uploaded. The big change to this version is the inclusion of a system to import data from versions of Timesheets Lite prior to version 3. Note that databases from the free version of Timesheets Lite cannot be imported. You can email those databases to us and we'll upgrade them for you. Here's a list of the changes:

• Added Data Import tool for bringing in data from versions of Timesheets Lite prior to Version 3.0.1. Can be found on the Tools->Import Data menu. Note that this will not work for importing data from the free version of Timesheets Lite. We have an in-house tool to do this so please email us your free Timesheets Lite database if you'd like it imported into the current version of the software.
• Fixed up a problem with the "Frequently Used Projects" menu when using SQL Server or MySQL.
• The System Options page now allows selection of an Access database location while connected to a SQL Server or MySQL database.
• When the System Options page is used to connect to a new database the structure of the database is examined to ensure it's a valid Timesheets Lite database.
• Fixed up the reports that threw an error when just one employee was selected.
• Time description is now included on the Detailed Activity report.

We're just uploading version 3.0.3 of Timesheets Lite that addresses some networking issues and database access problems. Changes made to the version 3.0.3 include:

• Set the default application skin to Money Twins (the light blue skin used in all the screenshots on this site).
• Fixed a page ordering problem with the first run wizard.
• Resized the first run wizard window to a more sensible size.
• Added some more information to the error reporting form.
• Made some changes to the task timer to reduce database load including updating the time to the database every 10 seconds and changing the update method to a less data intensive procedure.
• Changed the database connection mode for the default Access backend to a more optimistic method and changed the data locking to record locking rather than page locking. Should result in less connection errors with heavily loaded systems.
• Stopped event logging for attempted loads of common activities and employees with an ID of 0.
• The software now closes database connections when they are not in use rather than having a persistent connection.