Re: Access 03 Security



I'm using this setup to give specific security permissions to certain users
of a DB on a corp shared drive. How ever i am finding some difficulty trying
to import data from queries into excel with this security format.

Please advise.

Thanks,
Larry

"Joan Wild" wrote:

"MFSCLARK" <MFSCLARK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5DC48D33-29F4-4933-9D7E-2631F101C73A@xxxxxxxxxxxxxxxx
It opens with security; however, if I go to My documents thru the windows
explorer and click on my database, it will open under the default mdw file
and that does not have securities.

If that's the case, then you missed a step in securing the mdb. You
shouldn't be able to even open the mdb using system.mdw.

What clicked and I hope this is my misunderstanding, on your article,
under
"Controlling and Viewing which MDW is in use" - "Start Access with
Different
Wrokgroup file" You say: "...you can start Access with a Command line
that
specifies to use a different MDW instead." IS there somewhere besides
the
desktop shortcut that I can place this command line?

No

To me is seems that it
would have to be in the database itself somewhere where it would be run
upon
opening the database.

No, the mdw is tied to a session of Access, not a database. You can setup
security such that a database can be used with a number of mdw files; and
you can have many databases that will open using one mdw file.

Access always uses security. It ships with a mdw named system.mdw that is
used for every session. You are silently logged in as 'Admin' using this
mdw for unsecure sessions. Access always has some mdw that is set as the
default one to use (that would be in effect if you just opened Access, or
opened a mdb file from Windows Explorer). You can change the default via
the workgroup administrator, or you can use a desktop shortcut with the
/wrkgrp switch to override the default *for just that session* of Access.
Once you've opened a session of Access using a secure mdw, you can open any
number of mdb files during that session, and you're still using the secure
mdw.

How else will the wkjgrp.mdw get activated if a person
clicks it from the Windows Explorer File????

Your choice is to use/distribute a desktop shortcut, or change each
computer's default mdw to your secure mdw. The former is preferred, since
users likely have unsecured databases and if you join them by default to
your secure mdw, they'd get a login prompt for every session of Access.

--
Joan Wild
Microsoft Access MVP


.



Relevant Pages

  • Re: security wizard cannot be run
    ... and a potentially naive question - if security details are held in an mdw ... "Joan Wild" wrote: ... So now I assume I have to apply security from the start. ... Then I have to split the database and copy the FE and the shortcut to ...
    (microsoft.public.access.security)
  • Re: Use Level Security lockout
    ... MDW to open your database with some specialized permissions. ... see if I could use it to open the MDB with the correct credentials. ... Here are a number of links about security: ...
    (microsoft.public.access.security)
  • Re: Use Level Security lockout
    ... What I mean is the application that the Access 2.0 database drives will not ... tables because of the security issues. ... this was changed to MDW, ... you use it to open the MDB? ...
    (microsoft.public.access.security)
  • Role Based Security Question
    ... I have a few questions about role based security in an ASP.Net application. ... Page - Role relationships are also held in a database. ... Here are the goals we are trying to accomplish: ... the pages the user has access to into the Session object on Session_Start. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Role Based Security Question
    ... I have a few questions about role based security in an ASP.Net application. ... Page - Role relationships are also held in a database. ... Here are the goals we are trying to accomplish: ... the pages the user has access to into the Session object on Session_Start. ...
    (microsoft.public.dotnet.framework.aspnet)