Why can't 2K/XP users run ART without Admin Rights?

[TheMorphius]

I'm new to this forum so forgive me if I'm not up to speed with etiquette.

The question I have must surely have been asked elsewhere but I have yet to find a meaningful answer or solution so here goes.

I am trying to deploy a VB/Access application within a client server environment. I have a database that sits on the server where users can only access it via VB remote automation and an ActiveX component. So far so good. I then have a database specifically for access reports which is deployed on each client workstation. The client workstation in most cases will not have the retail version of Access, so Access Runtime 2000/2003 is deployed as part of the client installation process

The problem I am experiencing is that if the user has full admin rights to their workstation, Access Runtime will run without a problem when I Shell execution from a VB application to invoke MSACCESS.EXE with various command line switches to interrogate the "secure" database. However, should the client not be allowed admin rights to their workstation, Access Runtime fails to be invoked.

Does anyone know why ART expects the client workstation to have full Admin rights to be invoked, or indeed what is ART trying to do in Admin mode that it can't do in non Admin mode?

I imagine it is something to do with a registry setting cos I cannot believe Microsoft expects every client workstation within a corporate environment to have Admin rights as that might just compromise OS security a little.

Any gurus out there - please help! Any solution offered will be tried desparately and immediately!

Thanx

 

[John.Woody]

You may find that the rights of the user do not allow them to create / modify files on their workstation, where as the administrator has those rights. If that is the case you need to work with the network administrator to change their rights for the folder where your mdb is stored.