Re: Adding a database to existing workgroup file

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Joan: I went back and checked the User group permissions on the newly secured
database. The Users group has no permissions at all (I did check the database
permissions.) The Admin user is a member of that group, as are all other
users as well (as I read in instructions). The privileges are assigned to two
other groups.

With my original db, the only access to it was through the shortcut.
Double-clicking generated an error re not having permissions, as you pointed
out. Yet, I had rejoined the system.mdw file so I didn't have to log on to
dev versions of 4 other dbs under development. That was working fine until I
started the process of implementing security on a new db.

Now when I set up the new db to use the custom.mdw, 1) I can open the db
directly by double-clicking the file, which I should not be able to do. 2) As
of 1/2 hour ago, I can now also open my original db by double-clicking the
file, which I could not do earlier today, because I checked. 3) when I close
these dbs and Access as well, then reopen Access to rejoin the system.mdw
file, close Access, then reopen the two databases, and check their mdw file
in Security Manager, they are rejoined to the system.mdw file.

Perhaps my next step should be to recreate the custom.mdw file and start over.
--
susan


"Joan Wild" wrote:

> "Susan L" <SusanL@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:447B0FCD-146A-4777-8263-F6BDCC1B6BCE@xxxxxxxxxxxxxxxx
> > Joan, thanks for your response. You were (of course) right that I didn't
> > realize that I would need to remove privileges from the default User group
> > again. I did that (the Admin user was still in the User group, not the
> > Admins
> > group) and everything worked as it should.
> >
> > However, I still have a problem with "losing" the custom.mdw connection
> > when
> > I change back my copy of Access to the system.mdw file. I closed the new
> > db
> > after changing and testing permissions, opened Access from my MS Office
> > toolbar, rejoined the system.mdw, checked the new db, and voila! it was
> > back
> > to the system.mdw.
>
> What do you mean 'it was back to the system.mdw'? You just said you
> rejoined the system.mdw, so what else should it be back to?
>
> If you mean that you could open your secure db using system.mdw, then you
> didn't remove all permissions for the Users Group (check the database
> object). You shouldn't be able to even open the mdb while joined to
> system.mdw
>
>
> --
> Joan Wild
> Microsoft Access MVP
>
>
>
.

Relevant Pages

  • Re: Dont need security in Access 2007 or Access 2003
    ... but you should create a new database and import all objects - this will ... ensure that 'Admin' owns the database object and it is truly unsecured. ... permissions for every object. ... Not clear what is meant by 'Chose Groups, and then User Group' It looks ...
    (microsoft.public.access.security)
  • Re: would it be wise???
    ... >> exception of setting up some permissions for the user group). ... >> be why the admin user from the system.mdw can get in? ... >> user group permission to open/run the database, ...
    (microsoft.public.access.security)
  • Re: Run-time error 3326 and MDW file
    ... > I am trying to set-up an access 97 database so that my user group ... As this is the first time I have set-up the ... > I have set the user group so the table has no ticks set which I ... I would think you'd want to give them at least Read Data permissions on the ...
    (microsoft.public.access.security)
  • Re: Run-time error 3326 and MDW file
    ... >> I am trying to set-up an access 97 database so that my user group ... As this is the first time I have set-up the ... >> I have set the user group so the table has no ticks set which I ... you can remove all permissions and use run ...
    (microsoft.public.access.security)
  • Re: Adding a database to existing workgroup file
    ... Did you define a pwd for Admin in the custom mdw? ... I went back and checked the User group permissions on the newly secured ... The Users group has no permissions at all (I did check the database ... > these dbs and Access as well, then reopen Access to rejoin the system.mdw ...
    (microsoft.public.access.security)