I have the fix from Microsoft, although you will need to create or modify your
own MST to resolve the issue. MS have no date for a fix to the MSI package
itself.

You need to all the following entries to the MST:

RegKey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engi nes\Excel\win32
Type: STRING
Value: C:\Program Files\Microsoft Office\OFFICE11\msaexp30.dll


RegKey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engi nes\Excel\win32old
Type: STRING
Value: C:\Windows\System32\msexcl40.dll



I implemented I slightly more elegant solution by doing an AppSearch for win32
and using this for the win32old value. I also made both keys part of the
component that msaexp30.dll resides in. If you're happy modifiying MSI/MST
tables through Orca etc, here's the changes:


AppSearch table (1 entry):

Property: JET4EXCEL
Signatu JetWin32Reg



RegLocator table (1 entry):

Signatu JetWin32Reg
Root: 2
Key: SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
Name: win32
Type: 2



Registry table (2 entries):

Registry: Access.SP2Fix1
Root: 2
Key: SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
Name: win32old
Value: [JET4EXCEL]
Component: Global_Access_Core

Registry: Access.SP2Fix2
Root: 2
Key: SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
Name: win32
Value: [#MSAEXP30.DLL]
Component: Global_Access_Core



Regards
Jon Abbott
Clarksons Plc