Access 2003 Reinstalls Every Time



Hi! I previously had Office XP installed via Group Policy on several
workstations, and for various reasons outlined elsewhere on the site, I
upgraded to Office 2003. At the time I upgraded, I didn't know anything about
what a Group Policy was (our IT guy left the company some time back, and as
of yet we haven't been able to replace him). So when shortcuts to Office XP
kept reinstalling itself after every reboot, I tried various things to stop
it before I learned (through this site, actually) about Group Policies and
what actually went wrong.

The solution, by the way, was to disable the Group Policy and THEN upgrade
to Office 2003.

We have eight workstations in the office, and two were used as guinea pigs.
On the two test computers, I had done full uninstalls and reinstalls prior to
finding my solution. On the rest, I upgraded from the original installs after
disabling the group policy. When I was finished, I installed SP3 on all
workstations.

On the six upgrades, every thing works fine. On the two that were done as
full installs, Access 2003 has to reinstall itself every time I open the
program up.

I did some research and found http://support.microsoft.com/kb/914830/ seemed
to at least address the problem. It gives advice on how to manually change
the registry:

<i>To resolve this problem, manually change the registry on the computer
where Access 2003 does not start as expected. To do this, follow these steps:
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel
3. In the right pane, right-click win32, and then click Modify.
4. In the Value data box, type the following, and then click OK:
C:\Program Files\Microsoft Office\OFFICE11\msaexp30.dll
Note This path is for the default location. If the Msaexp30.dll file is
located on another drive or in another folder, use the path of the actual
drive and folder.
5. Exit Registry Editor, and then start Access 2003. </i>

However, on the two computers in which I did full installs, the
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel" doesn't exist.
It exists on all computers that the upgrade was done on (I imagine it has
something to do with upgrading from a Group Policy, but I'm no expert), but
that doesn't really matter because SP3 addressed those issues.

So my question, finally, is if anyone knows how I can fix this problem on my
two guinea pigs? Is there a different place I can edit the registry? I have a
Win32 file in a "...Engines/Sharepoint" folder, but so does the six upgrades.

Any thoughts?
.



Relevant Pages

  • NT - 2003 and 98 - XP Upgrades
    ... and at the same time move 600+ workstations from 98 to XP. ... My question has to do with system policies. ... How do I upgrade an NT domain to 2003 and Windows 98 ... If I upgrade the domain and create group policy settings the 98 clients will ...
    (microsoft.public.windows.server.migration)
  • RE: [opensuse] syslog stuff
    ... syslog-ng became available as an alternative to syslogd. ... I have always done upgrade installs because I have certain software ... where an obsolete package was left in place along with the new ...
    (SuSE)
  • Re: Windows XP and Group Policy Preferences
    ... the print$ share on our print server has only domain users group ... Event Source: Group Policy Printers ... Also check to see if the printer installs properly if the drivers for ...
    (microsoft.public.windows.group_policy)
  • Re: From VFP7 to 8 or 9?
    ... unwilling to upgrade to the latest version of my apps. ... to install the latest VFP runtimes, ... BTW, most of those workstations are still W98, so that should tell you ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Installing Access 2000 or Access 2003 using Vista
    ... mention that I actually had done the installs and they work for me. ... Since I already had an A2000 version of my app, ... it was easier to just upgrade them than try to fix some pesky problem I ... that earlier Access will not run on Vista. ...
    (microsoft.public.access.setupconfig)

Loading