Permissions on one Work Group but two different databases

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have created a DB with security and it works wonderful, but I have a
co-worker who is creating another DB that everyone in my work group will use
along with several other employees. The problem is that several of the
employees on my work group have Update or New permissions and my co-worker
would like read only access to them. We have tried to place read only
permissions on the tables, queries, etc., but with no luck. In some
instances they can't type, but when they try and view other forms through a
command button (visual data) they can not see them. Any ideas will help!
 
Jennifer said:
I have created a DB with security and it works wonderful, but I have a
co-worker who is creating another DB that everyone in my work group
will use along with several other employees. The problem is that
several of the employees on my work group have Update or New
permissions and my co-worker would like read only access to them. We
have tried to place read only permissions on the tables, queries,
etc., but with no luck. In some instances they can't type, but when
they try and view other forms through a command button (visual data)
they can not see them. Any ideas will help!
Click to expand...

Permissions are stored in the mdb file. Since your coworker has a separate
database, the permissions won't conflict. The workgroup file contains just
the usernames/groups/membership/passwords.

If you use RWOP (run with owner permission) queries, then users don't need
any permissions on the tables at all. Grant the necessary permissions on
the queries.
 
Silly question- where do I find more information on RWOP. I have never heard
of it before, but then again theis is the first time I have had to deal with
two DB on one Workgroup file.
 
I am sorry I keep bothering you, but after reviewing the RWOP information. I
am really not sure if it is what we need. The DB has a FE and and BE.
Nobody will be able to access the BE other than the ADMIN. In the FE my
coworker has command buttons that pop up other forms. Before we place
permissions on the DB everyone can log in and view all the forms fine but as
soon as we put permissions on it the forms are no longer viewable. We want
it set up where they can only read them and not insert any data. If RWOP is
what we need how does setting permission on the queries to owner permissions
keep them from updating, inserting, or deleting vital data.

Thanks for your patience with me. Jennifer
 
Jennifer said:
I am sorry I keep bothering you, but after reviewing the RWOP
information. I am really not sure if it is what we need. The DB has
a FE and and BE. Nobody will be able to access the BE other than the
ADMIN.
Click to expand...

I hope that you are referring to a user other than the built-in Admin user.
In the FE my coworker has command buttons that pop up other
forms. Before we place permissions on the DB everyone can log in and
view all the forms fine but as soon as we put permissions on it the
forms are no longer viewable. We want it set up where they can only
read them and not insert any data. If RWOP is what we need how does
setting permission on the queries to owner permissions keep them from
updating, inserting, or deleting vital data.
Click to expand...

You would first deny all permissions to the tables. Then (while logged in
as a user who has full permissions to the table) create a query and set it
to RWOP. Give the users permission to read data on this query and that's
all they'll be able to do. Even though they don't have permissions on the
tables, when they run the query they have the query owner's permission,
meaning they are running the query as though the owner is. They can access
the table data, but are restricted by the permissions they have on the
query.

Also give them permission to open the form.
 
I just wanted to say thanks for all of your help. We were able to fix the
problem by following your insturctions. Your help was greatly appreciated.

Jen
 
Back
Top