Inform Court Form Update - Ontario Labour Review Board Forms (OntLabor)

An update to the OntLabour form suite was released on July 29, 2009 for InForm court form subscribers. These changes are due immediately.

Updated Forms:

• A & C series forms requiring note paragraph re: Accessibility For Ontarians With Disabilities Act, 2005

If you have any further questions regarding this update, please contact us at Infoware Support.

New Version of ImportantDates+ Released!

The latest version of ImportantDates+ was released on July 14, 2009.

The IDWorkstation component now allows users to set a Reminder Pattern that can span up to 10 years by selecting the "Monthly" Reminder Pattern and entering the number "120" (12 months x 10 years) in either "Number of Months" boxes. Previously this number was limited to 12 months.

This version also fixes an issue with both the IDWorkstation component (version 1.1.0.5) and the IDMessenger back-end server application (version 2.1.0.5) that was preventing the NextReminderDate from being recalculated correctly when the Reminder Pattern was set to "Monthly".

Word 2007 serious Bug in KB969604 released June 9, 2009

This is an urgent issue!

The security patch released by Microsoft as KB969604 has a serious flaw that results in Document Variables being corrupted in any Word document that you edit and save. This flaw is also contained in Office 2007 SP2 service pack.

Word LX uses document variables to control a number of features in the system. The most obvious one is named "papertype" and controls the way MultiPrint sends documents to the printer. When you print using "Final" the value of the "papertype" variable is used to decide what paper source to use during the print job. The Microsoft patch corrupts this value and the document will no longer print as expected. This corruption appears to happen in both docx and compatibility mode doc style documents created edited with Word 2007!

There are two methods work around this serious bug:

• You must uninstall both SP2 for Office 2007 and uninstall the KB969604 patch and mark these to be ignored by any automatic Windows Update mechanisms (so they aren't automatically re-installed)

OR

• Request and install the Microsoft Hot Fix ID KB970942 (posted June 30, 2009). As with all hot fix patches this should be tested in your environment before deployment! Our initial testing indicates that this hot fix does fix the problem, however we do not know at this point if it causes any others!