Securing DB with Workgroup File davecoats622 23.02.2006 20:32:36 I have a database which is spilt into a front end and a back end. When I am building the Security Workgroup file, should I build one for the Front end and then build an identical one for the Back end? I am accessing the program through a Desktop shortcut which points to the Workgroup file. If I have a wrkgrp file for the front end and back end, which one should I point to in my shortcut?

Re: Securing DB with Workgroup File "Rick B" <Anonymous> 23.02.2006 20:41:20 You only need one workgroup file - period. You can have many database files secured to one workgroup file. In our office, we have one secured workgroup file that lives on the server and it contains all the Users and Groups for my department. We secure almost all of our shared databases to this one workgroup. -- Rick B "davecoats622" <davecoats622[ at ]discussions.microsoft.com> wrote in message news:166C1C95-2F82-47B2-98C9-DD1955484D49[ at ]microsoft.com... [Quoted Text] >I have a database which is spilt into a front end and a back end. When I >am > building the Security Workgroup file, should I build one for the Front end > and then build an identical one for the Back end? I am accessing the > program > through a Desktop shortcut which points to the Workgroup file. If I have > a > wrkgrp file for the front end and back end, which one should I point to in > my > shortcut?

Re: Securing DB with Workgroup File davecoats622 23.02.2006 20:59:27 If you only have one workgroup file, how do you apply security to objects in the backend? I ran the security wizard using my front end so does that mean only the objects in the front end will be secured with permissions? Thanks for your help. "Rick B" wrote: [Quoted Text] > You only need one workgroup file - period. You can have many database files > secured to one workgroup file. > > In our office, we have one secured workgroup file that lives on the server > and it contains all the Users and Groups for my department. We secure > almost all of our shared databases to this one workgroup. > > -- > Rick B > > > > "davecoats622" <davecoats622[ at ]discussions.microsoft.com> wrote in message > news:166C1C95-2F82-47B2-98C9-DD1955484D49[ at ]microsoft.com... > >I have a database which is spilt into a front end and a back end. When I > >am > > building the Security Workgroup file, should I build one for the Front end > > and then build an identical one for the Back end? I am accessing the > > program > > through a Desktop shortcut which points to the Workgroup file. If I have > > a > > wrkgrp file for the front end and back end, which one should I point to in > > my > > shortcut? > > >

Re: Securing DB with Workgroup File "Rick B" <Anonymous> 23.02.2006 21:18:13 I have not set up security on a new file in a while. I believe that I simply opened the database while joined to the workgroup, and then took away the access from the Users group. Check out the following links and they should set you straight. There are a couple of MVPs that are really good with security issues, so maybe one of them will jump in and give you a quick answer. Joan? Lynn? You there? :-) -- Rick B Security FAQ http://support.microsoft.com/?id=207793 The Security Whitepaper is also worth reading to help you understand. http://support.microsoft.com/?id=148555 Joan Wild: www.jmwild.com/AccessSecurity.htm Lynn Trapp http://www.ltcomputerdesigns.com/Security.htm "davecoats622" <davecoats622[ at ]discussions.microsoft.com> wrote in message news:AA2A2287-361A-4B91-9A86-EC19AB4C80BE[ at ]microsoft.com... [Quoted Text] > If you only have one workgroup file, how do you apply security to objects > in > the backend? I ran the security wizard using my front end so does that > mean > only the objects in the front end will be secured with permissions? > Thanks > for your help. > > "Rick B" wrote: > >> You only need one workgroup file - period. You can have many database >> files >> secured to one workgroup file. >> >> In our office, we have one secured workgroup file that lives on the >> server >> and it contains all the Users and Groups for my department. We secure >> almost all of our shared databases to this one workgroup. >> >> -- >> Rick B >> >> >> >> "davecoats622" <davecoats622[ at ]discussions.microsoft.com> wrote in message >> news:166C1C95-2F82-47B2-98C9-DD1955484D49[ at ]microsoft.com... >> >I have a database which is spilt into a front end and a back end. When >> >I >> >am >> > building the Security Workgroup file, should I build one for the Front >> > end >> > and then build an identical one for the Back end? I am accessing the >> > program >> > through a Desktop shortcut which points to the Workgroup file. If I >> > have >> > a >> > wrkgrp file for the front end and back end, which one should I point to >> > in >> > my >> > shortcut? >> >> >>

Re: Securing DB with Workgroup File "Rick B" <Anonymous> 23.02.2006 21:22:12 In the JMWILD link http://www.jmwild.com/security02.htm Step 18 states that you should choose to create a new workgroup information file. If I remember correctly, you are given the option to use an existing one at that point. -- Rick B "davecoats622" <davecoats622[ at ]discussions.microsoft.com> wrote in message news:AA2A2287-361A-4B91-9A86-EC19AB4C80BE[ at ]microsoft.com... [Quoted Text] > If you only have one workgroup file, how do you apply security to objects > in > the backend? I ran the security wizard using my front end so does that > mean > only the objects in the front end will be secured with permissions? > Thanks > for your help. > > "Rick B" wrote: > >> You only need one workgroup file - period. You can have many database >> files >> secured to one workgroup file. >> >> In our office, we have one secured workgroup file that lives on the >> server >> and it contains all the Users and Groups for my department. We secure >> almost all of our shared databases to this one workgroup. >> >> -- >> Rick B >> >> >> >> "davecoats622" <davecoats622[ at ]discussions.microsoft.com> wrote in message >> news:166C1C95-2F82-47B2-98C9-DD1955484D49[ at ]microsoft.com... >> >I have a database which is spilt into a front end and a back end. When >> >I >> >am >> > building the Security Workgroup file, should I build one for the Front >> > end >> > and then build an identical one for the Back end? I am accessing the >> > program >> > through a Desktop shortcut which points to the Workgroup file. If I >> > have >> > a >> > wrkgrp file for the front end and back end, which one should I point to >> > in >> > my >> > shortcut? >> >> >>

Re: Securing DB with Workgroup File "Joan Wild" <jwild[ at ]nospamtyenet.com> 24.02.2006 22:32:15 You don't mention the version, but I'll assume a recent one. You have secured the objects in the frontend only at this point. You can open the frontend via the shortcut you have on your desktop. By doing so, you'll be using the secure mdw. You can just hit Ctrl-N and create a new database. Import the tables from the backend, and then go via the Tools, security, permissions dialog to 1. Remove all permissions for all objects for the Users Group. 2. Proceed to assign permissions to your groups. -- Joan Wild Microsoft Access MVP davecoats622 wrote: [Quoted Text] > If you only have one workgroup file, how do you apply security to > objects in the backend? I ran the security wizard using my front end > so does that mean only the objects in the front end will be secured > with permissions? Thanks for your help. > > "Rick B" wrote: > >> You only need one workgroup file - period. You can have many >> database files secured to one workgroup file. >> >> In our office, we have one secured workgroup file that lives on the >> server and it contains all the Users and Groups for my department. >> We secure almost all of our shared databases to this one workgroup. >> >> -- >> Rick B >> >> >> >> "davecoats622" <davecoats622[ at ]discussions.microsoft.com> wrote in >> message news:166C1C95-2F82-47B2-98C9-DD1955484D49[ at ]microsoft.com... >>> I have a database which is spilt into a front end and a back end. >>> When I am >>> building the Security Workgroup file, should I build one for the >>> Front end and then build an identical one for the Back end? I am >>> accessing the program >>> through a Desktop shortcut which points to the Workgroup file. If >>> I have a >>> wrkgrp file for the front end and back end, which one should I >>> point to in my >>> shortcut?

Re: Securing DB with Workgroup File "Albert D.Kallal" <PleaseNOOOsPAMmkallal[ at ]msn.com> 05.03.2006 23:10:29 davecoats622" <davecoats622[ at ]discussions.microsoft.com> wrote in message news:AA2A2287-361A-4B91-9A86-EC19AB4C80BE[ at ]microsoft.com... [Quoted Text] > If you only have one workgroup file, how do you apply security to objects > in > the backend? I ran the security wizard using my front end so does that > mean > only the objects in the front end will be secured with permissions? > Thanks > for your help. you simply join the workgroup file You then open up the back end...and start setting your permissions... You seem to be missing a point that you can setup security manually here.. The wizard does nothing that you can't do manually, and nothing in the mdb file is changed in a special way when you setup security yourself....or use the wizard. remember, when you launch ms-access, you MUST have a workgroup security file set. You THEN open a database file AFTER you logged in, and launched ms-access. So, the workgroup security file is where users, and passwords are. And, if done correctly, you NEVER EVER assign permissions to users to individual objects in a database. You ALWAYS assign users to security groups...right? Do this means that permissions of users is NEVER in the actually database files..but ALWAYS remains in the workgroup file. If you do this, then you can send update to your customers that you built databases for..and they will NEVER loose their security settings...since they always assign users to your security groups that you created... -- Albert D. Kallal (Access MVP) Edmonton, Alberta Canada pleaseNOOSpamKallal[ at ]msn.com http://www.members.shaw.ca/AlbertKallal