97 Runtime problems in XP limited user account
Posted on 2004-10-20
We are having several problems with a 97 runtime application running in various XP environments when the user is a limited account. We are using Wise and the SageKey scripts to build the install, and everything works fine as long as the account used to install the program is the same account used to run it. But we have some clients who understandably want to do the install from one account and have the user run it from another account.
Our errors have included:
1. on startup, "can't be started - was unable to initialize the Windows registry" error (this occurs when Access XP is also installed)
2. on exit from app, "you do not have access to make the required system configuration modifications" (this occurs on limited user accounts in a client-server setup)
3. within app, 3027 error when reattaching to back end tables unless we are running from the same account that did the runtime install - even another admin account gets this error.
I think all of these issues probably have to do with the user not being able to update the registry. My questions are:
1. Are there people out there successfully running 97 runtime fe/be apps in XP limited user accounts? or is that too much to ask?
2. Is there a "run as" option or other workaround that consistently works? Our testing with "run as" has had problems, too.
I have not been successful at finding anything on the web which specifically addresses 97 runtime in a limited XP user environment.