MSACCESS 2003 Fails After SP2 Update

M

Michael

Jon:

Honestly, I did not try it because I've had other things that are currrently
keeping me busy. I went back to SP1 and am hoping that a SP2 hotfix will be
available shortly.

Unfortunately, I need a post-SP2 hotfix for Excel that was developed for me.
I may have to address the Access problem again myself if I need to use the
updated Excel in the near future.

Michael
 
M

Michael

Jon:

Honestly, I did not try it because I've had other things that are currrently
keeping me busy. I went back to SP1 and am hoping that a SP2 hotfix will be
available shortly.

Unfortunately, I need a post-SP2 hotfix for Excel that was developed for me.
I may have to address the Access problem again myself if I need to use the
updated Excel in the near future.

Michael
 
M

Michael

Jon:

Honestly, I did not try it because I've had other things that are currrently
keeping me busy. I went back to SP1 and am hoping that a SP2 hotfix will be
available shortly.

Unfortunately, I need a post-SP2 hotfix for Excel that was developed for me.
I may have to address the Access problem again myself if I need to use the
updated Excel in the near future.

Michael
 
M

Michael

Jon:

Honestly, I did not try it because I've had other things that are currrently
keeping me busy. I went back to SP1 and am hoping that a SP2 hotfix will be
available shortly.

Unfortunately, I need a post-SP2 hotfix for Excel that was developed for me.
I may have to address the Access problem again myself if I need to use the
updated Excel in the near future.

Michael
 
M

Michael

Jon:

Honestly, I did not try it because I've had other things that are currrently
keeping me busy. I went back to SP1 and am hoping that a SP2 hotfix will be
available shortly.

Unfortunately, I need a post-SP2 hotfix for Excel that was developed for me.
I may have to address the Access problem again myself if I need to use the
updated Excel in the near future.

Michael
 
M

Michael

Jon:

Honestly, I did not try it because I've had other things that are currrently
keeping me busy. I went back to SP1 and am hoping that a SP2 hotfix will be
available shortly.

Unfortunately, I need a post-SP2 hotfix for Excel that was developed for me.
I may have to address the Access problem again myself if I need to use the
updated Excel in the near future.

Michael
 
M

Michael

Jon:

Honestly, I did not try it because I've had other things that are currrently
keeping me busy. I went back to SP1 and am hoping that a SP2 hotfix will be
available shortly.

Unfortunately, I need a post-SP2 hotfix for Excel that was developed for me.
I may have to address the Access problem again myself if I need to use the
updated Excel in the near future.

Michael
 
M

Michael

Jon:

Honestly, I did not try it because I've had other things that are currrently
keeping me busy. I went back to SP1 and am hoping that a SP2 hotfix will be
available shortly.

Unfortunately, I need a post-SP2 hotfix for Excel that was developed for me.
I may have to address the Access problem again myself if I need to use the
updated Excel in the near future.

Michael
 
J

Jon Abbott

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\Engines\Excel\win32
Type: STRING
Value: C:\Program Files\Microsoft Office\OFFICE11\msaexp30.dll


RegKey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\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
Signature: JetWin32Reg



RegLocator table (1 entry):

Signature: 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
 
J

Jon Abbott

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\Engines\Excel\win32
Type: STRING
Value: C:\Program Files\Microsoft Office\OFFICE11\msaexp30.dll


RegKey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\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
Signature: JetWin32Reg



RegLocator table (1 entry):

Signature: 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
 
J

Jon Abbott

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\Engines\Excel\win32
Type: STRING
Value: C:\Program Files\Microsoft Office\OFFICE11\msaexp30.dll


RegKey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\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
Signature: JetWin32Reg



RegLocator table (1 entry):

Signature: 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
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Installing Office-97 pro after uninstalled Office-2000 premium 5
Access 2003 and excel 0
When you start MSACCESS, Windows Installer starts 9
VSTO C# add in Outlook.Appointment error 0
Running Access97 And AccessXP on Windows Server 2003 terminal services 3
Vista and MSAccess Runtime 1
Office 2007 SP2 installation 0
Access 2003 fails to open from mdb file 2

Top