Access 2003/2007 always launches Installer

[Stephen]

Hi Folks,

This is killing me...

I've got a dual installation of Office 03-SP3/07-SP2 on an XP Pro SP3 box.
Every time I would alternately launch Word/Excel/etc. the Windows Installer
would run. I've found posts with fixes that have taken care of all but
Access. This is the current state of things...

If I launch Access 2003 the installer will run if I have previously launched
Access 2007. If I then close and launch A-03 for a second consecutive time
the installer will NOT run but it will run the next time I launch A-07. If I
launch in the order of A-03, A-07, A-03, A-07, the installer will run each
and every time!

Please... for the love of all things good and pure, someone tell me there is
a fix for this!!!

TIA!

 

[CJ]

Hi Stephen

It is my understanding that what you are experiencing is normal and
required. The exact same thing happens to me. I believe that part of the
Office 2007 upgrade included a major overhaul of the Access jet database and
so the installer has to run to load the correct drivers for your file. If it
didn't you would end up with a lot of corrupt 2003 databases.

That is how it was explained to me.

 

[Stephen]

Yeah, I've been doing some back reading and that does indeed seem to be the
case. I've also read of an elusive register hack that can help overcome this
but I've wasted enough time on this already. I do hope this bother enough
people that Microsoft figures out a way to avoid this annoyance.

Thanks for the confirmation.

 

[Tony Toews [MVP]]

It is my understanding that what you are experiencing is normal and
required. The exact same thing happens to me. I believe that part of the
Office 2007 upgrade included a major overhaul of the Access jet database and
so the installer has to run to load the correct drivers for your file. If it
didn't you would end up with a lot of corrupt 2003 databases.

Well, MS did come out with ACE a new version of the Jet database
engine to work with new SharePoint compatible fields in ACCDB files.
But it really has nothing to do with corrupt A2003 databases.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/

 

[Tony Toews [MVP]]

This is killing me...

No, there's no good solution other than ensuring you have A2007 SP1 or
newer installed which greatly decreases the installer time.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/