runtime and system.mdw security

  • Thread starter Thread starter Jane Levis
  • Start date Start date
J

Jane Levis

Im using a database splitted in Front-End and Back-end for
the datas.
The front-end is distributed via the access runtime and
linked to a system.mdw security workgroup.

When I want to add a new user it look like I have to
rebuild and distribute the runtime again if I want that
this new user recognized...

What is the solution ?

Thanks a lot
 
You should always apply permissions to groups, rather than to
individuals. If done this way, you simply add the new user to the
correct group, and they inherit all the correct permissions.
Furthermore, the data permissions properly belong on the backend to
properly secure the information. See the document on the website in my
signature for a full explanation.


Im using a database splitted in Front-End and Back-end for
the datas.
The front-end is distributed via the access runtime and
linked to a system.mdw security workgroup.

When I want to add a new user it look like I have to
rebuild and distribute the runtime again if I want that
this new user recognized...

What is the solution ?

Thanks a lot
Click to expand...


=======================================================
Jack MacDonald
remove UPPERCASE LETTERS from email address
Vancouver, B.C. Canada
Info about MSAccess user-level security
www.geocities.com/jacksonmacd
 
Jane Levis said:
Im using a database splitted in Front-End and Back-end for
the datas.
The front-end is distributed via the access runtime and
linked to a system.mdw security workgroup.

When I want to add a new user it look like I have to
rebuild and distribute the runtime again if I want that
this new user recognized...

What is the solution ?

Thanks a lot
Click to expand...


The list of valid users is contained entirely within the wokgroup
file. Perhaps you could just distribute a zipped copy of the updated
workgroup file?

TC
 
Back
Top