Re: Access db accessibility (permissions??)

The application requires no permissions of it's own. It doesn't write to the
registery in any manner. It's a vb app, the sole purpose of which is to
enter and modify data into an initialized Access database. As I said
earlier, when people take the installation cd home and install it on their
own systems there's absolutely no problem. However, when they get back into
the work environment where Sys Admins have systems locked down and the users
don't even have the permissions to install apps on their own systems they
can't get to the Access database. The first thing that happens when a user
loads the vb application is they are asked to log on with a predefined userid
& password. This doesn't happen when they are using their work systems
however on their personal systems at home eveything works correctly. This
lead me to surmise there some permissions that are set as default in Access
that are causing this to fail in a "locked down" system. The error that's
generated on an attempt to connect to the database is: error - 91: "Object
variable or with block variable not set".

I've checked to make sure my users have RWED permissions on the folder in
which the application and Access database are installed. So that's not an
issue.
"TC" wrote:

> It's a bit hard to say, when all you've really told us is that the
> users "can't open the database".
>
> Perhaps some code within the app itself, is trying to do something that
> requires administrative priviliges; eg. writing into certain areas of
> the registry?
>
> How about explaining /why/ the users "can't open the database" & what
> you actually mean by that.
>
> HTH,
> TC
>
>
.

Relevant Pages

  • Re: More before-the-fact advice for 2K and XP?
    ... neither ActiveX nor BHO require Admin permissions to ... given that non-admins have a significant amount of control over ... "Would you like to install the ... With executable white listing, the app doesn't just ...
    (microsoft.public.security)
  • Re: XP and the I875 ( IC7-G in this case)
    ... There is a way to provide drivers that are newer than ... when XP shipped into the install, but it is not a cake-walk. ... if the account in use does not have permissions ... >>greyed in the app and unable to make the change directly ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Design Guidelines for Non-Power Users?
    ... Non-Power Users and Admins will not be able to install your app. ... You can get whatever this folder happens to be by ... If they don't have write permissions, ...
    (microsoft.public.vb.general.discussion)
  • Re: Design Guidelines for Non-Power Users?
    ... Non-Power Users and Admins will not be able to install your app. ... You can get whatever this folder happens to be by ... If they don't have write permissions, ...
    (microsoft.public.vb.winapi)
  • Re: Problems running programs when users have restricted local permissions
    ... Usually an app needs grant to Users of Modify on some ... part within its install location. ... > at least Power User permissions. ...
    (microsoft.public.windowsxp.security_admin)