Read-Only User-Groups

[Mike M]

I have a simple secured database that I'm attempting to access via ADO.NET
from an ASP.NET page. The access database contains several users contained
in a few different user groups. I can successful connect to the database
when the connection string specifies a user that is a member of Admins or
Full Data User groups. However, user's with only User and Read-Only
permissions can not connect to the db. The OleDbException thrown by ADO.NET
is

You do not have the necessary permissions to use the
'C:/<path>/<filename>.mdb' object. Have your system administrator or the
person who created this object establish the appropriate permissions for
you.

Any thoughts as to why a user with Read-Only access would be denied access
to the db?

Thanks for the help...

 

[GVaught]

All users must have read/write/modify settings to the database, otherwise
they won't be able to open the database.

 

[Mike M]

I agree with you that full data access is required to open the database
since I was experimenting with the various level of permissions and found
that to be the only solution but I would like to have stronger security
measures in place. Is it possible to open the database with appropriate
permission levels then demote the user to read-only permission? Basically,
what is the point of having a Read-Only Group in the database security
environment if the members of the read-only group can not open the database
for SQL SELECT operations?

If you could clarify for me....when a secured database is started with the
following command-line what level of permissions are in place at startup of
MSAccess...

c:\> msaccess.exe <path to database file>.mdb /wrkgrp <path to workgroup
info file>.mdw

Is this sequence of actions taken by MSAccess in the ballpark...
1. MSAccess process created with security permissions based on the current
workstation user.
2. UserName/Password dialog prompt in MSAccess...enter user name and
password for Read-Only user. Open's the database ok.
3. Try to insert/update/delete a record, in a db table...MSAccess disables
those features since the current user context only has permissions to read.

Thanks for the time...

Cheers,
Mike