Re: Logging in to Access

User IDs and Passwords are part of the Workgroup, not the databse.

If you joined a workgroup with userid's and passwords, then you will have to
sign into it regardless of which database you are opening.

What you should do is rejoin the default mdw file which does not contain
passwords and use that to open all your files. If you do that you should
NOT be able to open up your 'secured' database. If you can, then you have
discovered tha tthe file is NOT actually secured and you need to go back to
the drawing board. You should get an error if you try to open it with the
default mdw.

Once you have confirmed all that, you can create a shortcut to your secured
database that includes the workgroup file in the path. This would cause the
file to open and the appropriate workgroup to be used. BUT, any other file
that you open will use the default workgroup (unless you include a workgroup
in your shortcut for those other fiels).


--
Rick B



"seth1980" <seth1980@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:27A955CB-4CE8-429C-BA1A-F0FB610137CD@xxxxxxxxxxxxxxxx
> Hi Everyone,
>
> My problem is this:
>
> I've created an access database (2003) on a shared drive for certain
people
> to use, but who have different levels of permission. However, after I've
> created my own administrator using the security wizard, EVERYTIME and
> EVERYWHERE I open an access database, it asks me for login information!!
>
> I only want this ONE database to use logins and no others. How do I set
this
> up so that I can keep this database on a shared drive and have the system
> only ask for login information when a user tries to open THAT particular
> database?


.

Relevant Pages

  • Re: Security Blunder
    ... passwords I setup dont work... ... but part is stored in a workgroup file. ... >> database on my system...All I get is the logon window with ...
    (microsoft.public.access.gettingstarted)
  • Re: ".Groups()" Collection Item not found (3265) on one of several computers only
    ... It exists in every Workgroup, but the text string being passed may not ... See http://www.QBuilt.com for all your database needs. ... Explicit" and "Require Variable Declaration" were good tips I knew ...
    (microsoft.public.access.security)
  • Re: Word 2003 Closes upon update of sort order of table using Acce
    ... Yes, I can only guess but suspect that when the developers tried to incorporate OLE DB, they probably found themselves with a lot more problems than they bargained for and probably too little time to design a better way through them. ... For an OLE DB data source you really need a .udl or .odc file rather than a DSN. ... It can be hard to tell because you can't inspect long file names within the database name text box. ... Both OLE DB and ODBC connections from Word can also suffer from another problem - if the pathnames of the access database and the workgroup security database are too long, you may have problems when you try to connect, or more likely, when you try to re-open the mail merge main document. ...
    (microsoft.public.word.mailmerge.fields)
  • Re: Security - Security & User Accounts
    ... You are currently joined to the workgroup file you secured ... password set so Access silently logs you into the database ... and then how can I set up secure logins for ...
    (microsoft.public.access.formscoding)
  • Re: store secured.mdw data on sql?
    ... When joining a workgroup, that Workgroup Information File will be opened in ... > itself determines the options under which it opens the fn.mdw at the time ... but database corruption still happens. ...
    (microsoft.public.access.security)