Prevent windows installer when open access 2007

[Jose]

Operatind system is windows xp
I have installed Access 2007 and Microsoft Office Access 2003 on the same
computer. When I run Access 2007 after you run Access 2003, Access 2007 takes
several minutes to repair itself and vice versa. Open windows installer.

I tried with access runtime 2007 and the same problem.

The users hate this popup, it is not friendly. The users have 3 applications
in access, 2 based access 2003 and 1 in access 2007. They open many times a
day and when they switch from access 2007 to 2003 or vice- versa always shows
the popup.

Thanks for any suggestion to avoid this popup.

Jose

 

[Jose]

No help about this issue form the link you posted

Any suggestions?

Thanks

 

[Tony Toews [MVP]]

Operatind system is windows xp
I have installed Access 2007 and Microsoft Office Access 2003 on the same
computer. When I run Access 2007 after you run Access 2003, Access 2007 takes
several minutes to repair itself and vice versa. Open windows installer.

I tried with access runtime 2007 and the same problem.

The users hate this popup, it is not friendly. The users have 3 applications
in access, 2 based access 2003 and 1 in access 2007. They open many times a
day and when they switch from access 2007 to 2003 or vice- versa always shows
the popup.

Can't be done. A2007 SP1 shortens that process but that's it.

Unless maybe you used some kind of virtualization process of some sort
for A2003 and A2007. I vaguely recall reading about one or two. Just
how well they work, how time consuming they are to setup and how
expensive they are I have no idea.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Jose]

Hi Tony,
I think is possible because I hear from a company that have a small software
to package access applications and one of their features is remove the repair
process.

Is expensive and I don't know if effectively they remove the repair process.

If you know someone or company who can fix this issue let me know to contact
them.

Thanks,
José Perdigão

 

[Pietro]

Hi Jose,

I have the same problem. There is not a better solution. The following hints
may help you:

Real life requirements make it quite common that several versions of Access
/ Access RT have to be installed side by side on the same computer.
Most common are
- compatibility issues that prevent a database from being upgraded
- third party applications dependencies which require a specific runtime
version (e.g. Sage)

Up to Office/Access 2003 the repair between the multiple versions was
somewhat annoying but tolerated since it completed within some seconds.
With Access 2007 the repair could take several minutes which is not
acceptable for users.


Version specific keys that trigger a Windows Installer repair:

Access 2007 (RTM)
=================
- The 'NoRepairNeeded' key is missing
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\Access\NoRepairNeeded]
@=""

- The version under the AccWiz CLSID key is < "8.1"
[HKEY_CLASSES_ROOT\CLSID\{53230322-172B-11D0-AD40-00A0C90DC8D9}\Version]
@="8.1"

- The 'CurVer' is not registered to 'Access.Application.12'
[HKEY_CLASSES_ROOT\Access.Application\CurVer]
@="Access.Application.12"


Access 2003 (SP3)
=================
- The 'NoRepairNeeded' key is missing
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Access\NoRepairNeeded]
@=""

- The version under the AccWiz CLSID key is < "8.1"
[HKEY_CLASSES_ROOT\CLSID\{53230322-172B-11D0-AD40-00A0C90DC8D9}\Version]
@="8.1"

- The Jet Excel ISAM key pointing to a wrong version of the isam dll
For an English default installation that would be
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel]
"win32"="C:\\Program Files\\Microsoft Office\\OFFICE11\\msaexp30.dll"
"win32old"="C:\\WINDOWS\\system32\\msexcl40.dll"


Access 2002 (SP3)
=================
- The 'NoRepairNeeded' key is missing
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\10.0\Access\NoRepairNeeded]
@=""

- The version under the AccWiz CLSID key is < "8.1"
[HKEY_CLASSES_ROOT\CLSID\{53230322-172B-11D0-AD40-00A0C90DC8D9}\Version]
@="8.1"


The Issue
=========
Access 2002 and 2003 will do a selfreg when the application is started which
registers some file extensions and
'[HKEY_CLASSES_ROOT\Access.Application\CurVer]' to the current version.
Access 2007 does no longer do the self register but as a result of another
related hotfix, any repair will delete the 'NoRepairNeeded' key for the 10.0
and 11.0 versions.
Since the self register introduces a bad keypath value for Access 2007 and
the Access 2007 repair deletes keypath values for Access 2002/2003 a Windows
Installer repair will always be triggered.

1) Use Softgrid to avoid side by side installation
2) Let Windows Installer complete the repair

3) Accept an unsupported configuration and ensure that the correct keypath
registry entries for 2007 are in place before Access is launched

 

[Jose]

Hi Pietro,
If I understood, make changes in registry as you wrote is it possible to
prevent the windows installer?

I can create a package and when I'm installing the access application the
installer package can make all changes that you wrote.
Let me know if this is the right way.

Thanks,
Jose

Hi Jose,

I have the same problem. There is not a better solution. The following hints
may help you:

Real life requirements make it quite common that several versions of Access
/ Access RT have to be installed side by side on the same computer.
Most common are
- compatibility issues that prevent a database from being upgraded
- third party applications dependencies which require a specific runtime
version (e.g. Sage)

Up to Office/Access 2003 the repair between the multiple versions was
somewhat annoying but tolerated since it completed within some seconds.
With Access 2007 the repair could take several minutes which is not
acceptable for users.


Version specific keys that trigger a Windows Installer repair:

Access 2007 (RTM)
=================
- The 'NoRepairNeeded' key is missing
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\Access\NoRepairNeeded]
@=""

- The version under the AccWiz CLSID key is < "8.1"
[HKEY_CLASSES_ROOT\CLSID\{53230322-172B-11D0-AD40-00A0C90DC8D9}\Version]
@="8.1"

- The 'CurVer' is not registered to 'Access.Application.12'
[HKEY_CLASSES_ROOT\Access.Application\CurVer]
@="Access.Application.12"


Access 2003 (SP3)
=================
- The 'NoRepairNeeded' key is missing
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Access\NoRepairNeeded]
@=""

- The version under the AccWiz CLSID key is < "8.1"
[HKEY_CLASSES_ROOT\CLSID\{53230322-172B-11D0-AD40-00A0C90DC8D9}\Version]
@="8.1"

- The Jet Excel ISAM key pointing to a wrong version of the isam dll
For an English default installation that would be
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel]
"win32"="C:\\Program Files\\Microsoft Office\\OFFICE11\\msaexp30.dll"
"win32old"="C:\\WINDOWS\\system32\\msexcl40.dll"


Access 2002 (SP3)
=================
- The 'NoRepairNeeded' key is missing
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\10.0\Access\NoRepairNeeded]
@=""

- The version under the AccWiz CLSID key is < "8.1"
[HKEY_CLASSES_ROOT\CLSID\{53230322-172B-11D0-AD40-00A0C90DC8D9}\Version]
@="8.1"


The Issue
=========
Access 2002 and 2003 will do a selfreg when the application is started which
registers some file extensions and
'[HKEY_CLASSES_ROOT\Access.Application\CurVer]' to the current version.
Access 2007 does no longer do the self register but as a result of another
related hotfix, any repair will delete the 'NoRepairNeeded' key for the 10.0
and 11.0 versions.
Since the self register introduces a bad keypath value for Access 2007 and
the Access 2007 repair deletes keypath values for Access 2002/2003 a Windows
Installer repair will always be triggered.

1) Use Softgrid to avoid side by side installation
2) Let Windows Installer complete the repair

3) Accept an unsupported configuration and ensure that the correct keypath
registry entries for 2007 are in place before Access is launched