:-)
Who wrote it? It must be doing something it should not. The developer should
figure out what that is and fix it. If you are just an end-user there is
little you can do.
To be fair, there could be other things that causes the program to fail. For
instance, it could be trying to access network resources that are only
available to a single user. Only by debugging the program would the developer
be able to determine what that is though. Again, it comes back to the fact
that the developer needs to fix the program.
"Randy" wrote:
> How is that done?
> --
> Thanks Randy
>
>
>
> "Jesper" wrote:
>
> > Yes. You re-architect the program so that it no longer requires admin
> > privileges. If it doesn't do anything administrative and still requires admin
> > privs it is flawed.
> >
> > "Randy" wrote:
> >
> > > I have a program that uses Microsoft access 2002. The program runs just fine
> > > when logon as Administrator. When I go to the user account I can not run the
> > > program. I am prompted for a admin logon. If I enter the admin account
> > > information the program will run but find the correct drive for the database.
> > > In any case I just want to allow the user to run this program not have to
> > > give them administrator rights. Is there a way to do this?
> > > --
> > > Thanks Randy
> > >
|
Similar Threads
