Strange Access 2002 Issue

I built an MST (through Office Resource Kit) to install MSAccess 2002. The users at my company have Access 97 installed. The software installed successfully. However, when they now try to launch Access 97, they receive the following error message:

Microsoft Access can't be started. Microsoft Access was unable to initialize the Windows Registry. Rerun Microsoft Access or Microsoft Office Setup to reinstall Microsoft Access.

I went over to one machine that was experiencing this issue. I logged in under my account (local admin) and was able to successfully launch Access 97 with no issues. Then I had the user log back in and the, viola, he application launched with no error! I went back and checked the MST but didn't see anything strange. I'm currently Googling this issue but I thought I would try the experts in the meantime. I'm thinking it's some kind of permissions issue. Has anyone come across an issue like this?

0 Comments   [ + ] Show comments

Answers (1)

Posted by: spartacus 13 years ago
Black Belt
Try giving Users full permission to the following registry key


It would still be worth your while Googling the general issues with multiple versions of Access on the same machine and the sort of coexistence issues you might face.

The general opinion seems to be that this can work as long as you install the versions of Access in chronological order (oldest version first, newest version last) and into separate folders. The main problem you might face is when double clicking on .mdb files and which version of Access launches when you do this.


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ