Linked database with user level security in work group file

[Guest]

Hi All,
I have an Access application that's basically 3 databases. One of them
linked to the tables on the other two. The other one is really a "front end"
with VBA code.
Security is controlled at user level (Read: work group file)

The application shortcut uses the command line parameters i.e.
[Access Path] [Database file path] /excl /wrkgrp [work group file]

The application is installed by an account that has Admin privilege.

If someone else without Admin privilege logs on, and tries to open the
application (clicking on the command line supplied shortcut), it says "Access
can't find the database file"

The weird thing is, even if you double click on the database file from
Windows explorer, it shows the same error.

When the non-Admin user tries join the work group, it says "Access Denied"

How can a non-Admin user use this secured database without, well, becoming
an Admin user?

I hope I explained it.

Any help is appreciated.

 

[Rick Brandt]

Hi All,
I have an Access application that's basically 3 databases. One of them
linked to the tables on the other two. The other one is really a
"front end" with VBA code.
Security is controlled at user level (Read: work group file)

The application shortcut uses the command line parameters i.e.
[Access Path] [Database file path] /excl /wrkgrp [work group file]

The application is installed by an account that has Admin privilege.

If someone else without Admin privilege logs on, and tries to open the
application (clicking on the command line supplied shortcut), it says
"Access can't find the database file"

The weird thing is, even if you double click on the database file from
Windows explorer, it shows the same error.

When the non-Admin user tries join the work group, it says "Access
Denied"

How can a non-Admin user use this secured database without, well,
becoming an Admin user?

I hope I explained it.

Any help is appreciated.

There are a total of four files here The three MDBs and the MDW. Does the
non-admin user have adequate permissions to the folders where all of these
reside?

 

[Guest]

There are a total of four files here The three MDBs and the MDW. Does the
non-admin user have adequate permissions to the folders where all of these
reside?

Thanks for the quick response.
The non-admin user just another windows user (regular windows account). So
there is no issue with folder permission.

May be updating the workgroup file needs Admin privilege?

 

[Rick Brandt]

Thanks for the quick response.
The non-admin user just another windows user (regular windows
account). So there is no issue with folder permission.

May be updating the workgroup file needs Admin privilege?

Are you sure? What version? For example Access 97 puts the default System.MDW
into the System32 folder which is a folder that a non-admin user wouldn't have
proper permissions for. It also uses areas of the registry that a non-admin
user doesn't have rights to. The newer versions solve those problems, but a
developer running with admin permissions could easily still put a resource in a
location that a non-admin user would have problems with.

 

[TC]

I can understand why Access would have to be installed from a windows
admins account. But why does your /application/ have to be installed
from a windows admins account?

TC

 

[Guest]

Are you sure? What version? For example Access 97 puts the default System.MDW
into the System32 folder which is a folder that a non-admin user wouldn't have
proper permissions for. It also uses areas of the registry that a non-admin
user doesn't have rights to. The newer versions solve those problems, but a
developer running with admin permissions could easily still put a resource in a
location that a non-admin user would have problems with.

Alright, here's some more info.

This is Access 2000.

The workgroup file resides on the same folder where the databases are.

I know system.mdw is in windows System folder, which a non-admin user does
not have access to. That brings another question. Does Access 2000 also uses
system.mdw?

 

[Guest]

I can understand why Access would have to be installed from a windows
admins account. But why does your /application/ have to be installed
from a windows admins account?

TC

Installation writes some information to the registry. Only a restricted
section of the application reads from it.

 

[Guest]

Alright, here's some more info.

This is Access 2000.

The workgroup file resides on the same folder where the databases are.

I know system.mdw is in windows System folder, which a non-admin user does
not have access to. That brings another question. Does Access 2000 also uses
system.mdw?

I don't know about you, but our system.mdw resides on a network share where
everyone can get to it. This allows me to make changes to permissions in one
place instead of having to goto each computer that needs permission to
different stuff. Normal users have read only permissions to this folder.
The error you are getting sounds like the user only has browse premissions
to the files, and since they are all in the same directory this is an issue,
because even if the user can join the workgroup they still won't be able to
access the DB.

Bill

 

[TC]

The name is the same, but different versions of Access can put it in
different folders.

HTH,
TC

 

[TC]

So, are you positive that a /non/ windows admims user, can actually see
the mdb file, in the place where it was installed by the windows admin
user program?

Here's what I'd try. Create, in the same folder where the shortcut
currently is, a new shortcut which points directly to the mdb file. No
msaccess.exe, no /wrkgrp switch & workgroup pathfilename. Just a normal
shortcut pointing directly to the mdb file. Then double-click it & see
what happens.

We'd expect you should get "insufficient permissions to open the
database" or whatever the message is. I'd be interested to know if you
/do/ get that message, or whether it still says "can't find database"
or words to that effect.

If you still get "can't find database", log back on as a windows admin
user, then try again. If it now says "insufficient permissions", then,
you know what the problem is: a non windows admin user, can not see the
mdb file, in the place where the windows admin user installation
program put it.

HTH,
TC