Re: setting up second application on same workgroup

Matthew Reed via AccessMonster.com wrote:
> I've already successfully implemented Access security for a front end
> and back end database, both mdb files. People run the front end mdb
> from their desktop with links to a back end mdb on the network
> (standard). Now I'm trying to add another pair of mdb files (a
> second application). The workgroup file is on the network too.
>
> Basically, when I run the Security Wizard to secure the second app,
> if I use the existing workgroup, it still allows anyone in the Users
> group into the database. If I build a new workgroup (I don't want
> to, but if it works, okay) I get locked completely out of the
> database file -- I can't open it as any user. I'm probably doing
> something wrong (Security Wizard?), but without saying much more
> about the details of what I've done you probably can't help too much.
>
> Still, any tips on doing this, pitfalls, whatever? Can I use the same
> workgroup or should I build a new one?
>
> Thanks!

You shouldn't even need the wizard for the second app. If you use your
secured workgroup file to open Access and then create the second file it
will automatically be secured under that workgroup. All you have to do is
set the permissions. If you already have the second one built you just need
to create a new blank file while using the secured workgroup and import
everything from your new app into the blank one.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com


.

Relevant Pages

  • Re: Database Ruined
    ... I had no idea setting up security could cause so many ... In a properly secured database, only the owner of that database has ... last time you can view these VERY important settings. ... use the exact same settings when recreating the workgroup. ...
    (microsoft.public.access.security)
  • Re: Security disapears from menubar when I add a new user
    ... > user logon and created an administrative logon called "sysadmin". ... > database owner is "sysop" and was used for development. ... by creating a new workgroup information file with a unique workgroup ... Security FAQ, ...
    (microsoft.public.access.security)
  • Re: Turn off Access security--no password provided
    ... Open Access (no database). ... see what workgroup you are currently joined to by default. ... > played around with the security settings in Access and long ago ...
    (microsoft.public.access.security)
  • Re: User and Workgroup was screwed
    ... system.mdw file after he implemented the security on the database. ... we tried to create a new mdw file by using those info in the text ... password in the workgroup. ...
    (microsoft.public.access.security)
  • Re: Sorting out security
    ... There is a link to it on the Security page of my website. ... > files and remote logins to a secured database. ... different name for the secure workgroup file. ... If the Admin user has no password then every user is ...
    (microsoft.public.access.security)
Loading