Security - Dropping security settings across a network??

[Jason]

Hi

I have set up a reasonably complex DB with the BE residing on a NT server and the FE on each clients computer. I have implemented full security and have several user groups and around 40 users. My workgroup file is on the server and everybody has a shortcut from thier workstation which directs them through this mdw file for the security. My problem is that each time I release a new front end, (which is developed on my computer with the same setup) and distribute it to the users, I seem to lose a lot of my previously saved security settings. Some of the users lose privileges to tables that they could previously update and I need to go around to each of the computers to check and change privileges. This confuses me because I thought I was sharing ONE mdw file (which I obviously never replace). Is there something local that is changing when I replace the front end. Also if I change the settings on one computer then go to another, I cant see the changed priveledge settings and I need to redo the procedure. I am definately routing everybody though the same .mdw file. I am having this problem continuously with several developed solutions. Has anybody seen this or does anyone have any advice?

Any help would be greatly appreciated.

Jason

 

[ghudson]

This is what I always do...

The .mdw file should be one each users computer where the front end is located. You should be using your own .mdw file on your computer. When you make changes to your front end and .mdw file, you will need to give the new versions to each user and ensure that they replace the new and overwrite their old files.

Their shortcut should join their front end with their .mdw file like this...
"C:\Program Files\Microsoft Office\Office\msaccess.exe" /wrkgrp "C:\Databases\Secured.mdw" "X:\Databases\Test.mdb" /user Testuser

HTH

 

[RichMorrison]

you wrote
<<
Is there something local that is changing when I replace the front end.
>>

Yes.
An "MDW" contains:
1) user names
2) group names
3) user to group memberships

The FE contains permissions. When you create a new FE you must set all the appropriate permissions BEFORE you distribute the FE to individual workstations.

BTW, there is little or no advantage from installing an FE on each desktop. The slight overhead of copying an FE from a server to a workstation is smaller that the time spent installing 40+ workstation copies whenever you change the FE.

RichM

 

[Jason]

Thanks a lot...

I will distribute the mdw file with the FE and make sure that the combination of the two contains the correct groups and users (mdw) and permissions (FE). I suppose that I could leave the mdw as shared on the network and just make sure that the FE permissions are up to date. At least the groups and users would be dynamic, (I have 2 people who have Admin rights as the site is very remote). This does seems a little bulky however as I would love to be able to sit at my desk, apply new permissions and have them permeate to the users without having to re-distribute the FE.

I am also quite concerned about your comment, RichM, about there being little or no advantage to having the FE reside on the individual workstations. There has been plenty of discussion in this forum regarding this topic with no really clear setup coming to the fore… I finally decided on the FE (workstation) BE (server) combination because I have to mail the updates to the site and have them distributed by one of the Admin personnel, (who walks from desk to desk and hits a self extracting .exe file). However it is a very slow network so I definitely need to have the most efficient setup. This would mean that for me, network traffic is the main concern. Is my setup best for this environment? Any thoughts/comments?

Thanks again

Jason

 

[RichMorrison]

Jason,

You wrote
<<
I finally decided on the FE (workstation) BE (server) combination because I have to mail the updates to the site and have them distributed by one of the Admin personnel, (who walks from desk to desk and hits a self extracting .exe file). However it is a very slow network so I definitely need to have the most efficient setup. This would mean that for me, network traffic is the main concern. Is my setup best for this environment? Any thoughts/comments?
>>

Yes your setup seems sensible in the given environment. My comment was unclear. I was assuming a single installation with a high-speed local network just because that's what I'm used to

The distribution issue you face is one of the reasons organizations go to Web-based apps. My current client is adopting an interesting strategy using "terminal services" where a local server has a Web portal that just shows the server desktop. Applications on the server can be standard Windows Access based and remote users enter via a standard browser.

RichM