Insights Toronto home
 
 
 
 

Problem: Conflict with Microsoft Jet 4.0 SP7 update

Applies to:
Insights Discovery 2.0, Insights Discovery 3.0.1

Summary:
On 25th June 2003, Microsoft issued an update to their "Jet" database technology through the Windows Update web site and downloadable from other locations. This update, displayed on the Windows Update web site as Recommended Update for Microsoft Jet 4.0 Service Pack 7 (SP7), contains a bug which affects access to Insights Discovery Reporting Language (DRL) files. The result is that errors appear when Insights Discovery starts up and subsequently whenever an attempt is made to switch to a different reporting language.

Symptoms:
When Insights Discovery starts up, or when an attempt is made to change the current reporting language, the following error message is displayed: “Insights Discovery failed to open the preferred reporting language database”. When the first error message is dismissed, a second appears: “A serious error has occurred. Please back up your database and re-install Discovery. If the problem still occurs please contact your software supplier. Press OK to exit Discovery.”

More Information:
Despite what the second error message says, Discovery will not exit immediately, and it may be possible to continue using the program if it was installed and in use before Jet 4.0 SP7 was installed. However, any attempts to change the reporting language will be unsuccessful, and if Jet 4.0 SP7 was installed before Discovery, then Discovery may exit unexpectedly and reporting will not be possible.

Resolution:
As an upgrade from Insights Discovery 2.0 to Insights Discovery 3.0 is available at no charge, no dedicated solution for Insights Discovery 2.0 will be developed. Discovery 2.0 users should upgrade to Discovery 3.0.

Discovery 3.0.1 users should download and apply the Insights Discovery 3.0.1 Refresh 1 patch. This will update the Discovery program to avoid the bug in the Microsoft Jet 4.0 SP7 update.

Acknowledgments:
Insights Learning & Development Ltd. would like to thank Microsoft Corporation for their help in identifying a solution to this problem.