Re: would it be wise???

The Users group should not have any permissions to any object in the
database.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Big List: www.ltcomputerdesigns.com/JCReferences.html


"tw" <tlsilveus@xxxxxxxxxxx> wrote in message
news:ecndHpgOFHA.2356@xxxxxxxxxxxxxxxxxxxxxxx
> What step did I miss then. I thought I followed the steps... (with the
> exception of setting up some permissions for the user group). Could that
> be why the admin user from the system.mdw can get in? I did give the user
> group permission to open/run the database, limit the number of
> modifications necessary if new groups are added. I guess I will move that
> permission elsewhere to prevent the admin user from getting in with the
> system workgroup file.
>
> "Jeff Conrad" <jeffc@xxxxxxxxxxxxxxxxx> wrote in message
> news:uI80NagOFHA.4052@xxxxxxxxxxxxxxxxxxxxxxx
>> Maybe this explanation will help you understand the process.
>>
>> Every time you open an Access database (without a shortcut
>> to give Access different instructions) Access will *attempt*
>> to log in as Admin user with no password. *If* that attempt
>> fails for any reason, then and *only* then will you be prompted
>> for a password.
>>
>> Does that help?
>>
>> --
>> Jeff Conrad
>> Access Junkie
>> Bend, Oregon
>>
>> "tw" wrote in message:
>> news:%23AwasFgOFHA.2132@xxxxxxxxxxxxxxxxxxxxxxx
>>
>>> if passwords are stored in the workgroup file, then the system workgroup
>>> file has no admin password. If the user logs in using the system
>>> workgroup
>>> file, the system will not ask for a password. Is this understanding
>>> incorrect?
>>>
>>>
>>> "Lynn Trapp" <ltrappNoSpam@xxxxxxxxxxxxxxxxxxxxx> wrote in message
>>> news:O3sAi1fOFHA.508@xxxxxxxxxxxxxxxxxxxxxxx
>>> > The better approach is to implement user level security properly, as
>>> > described in the Security FAQ, so that a person will not be able to
>>> > log on
>>> > as Admin without knowing Admin's password.
>>> >
>>> > --
>>> > Lynn Trapp
>>> > MS Access MVP
>>> > www.ltcomputerdesigns.com
>>> > Access Security: www.ltcomputerdesigns.com/Security.htm
>>> > Jeff Conrad's Big List: www.ltcomputerdesigns.com/JCReferences.html
>>> >
>>> >
>>> > "tw" <tlsilveus@xxxxxxxxxxx> wrote in message
>>> > news:e6S$7lfOFHA.2928@xxxxxxxxxxxxxxxxxxxxxxx
>>> >> Would it be wise to put in code upon start up, that if the
>>> >> CurrentUser()
>>> >> = 'Admin' then give user a message that they are using the wrong
>>> >> workgroup file and need to change to a proper workgroup file, then
>>> >> quit
>>> >> the system? If I were to do this, then I could possibly get locked
>>> >> out of
>>> >> my database if the workgroup file got corrupt? Could there be a way
>>> >> around getting locked out of the database if this code was
>>> >> implemented?
>>> >> If this code could be implemented, where should it go, on the start
>>> >> up
>>> >> form, or is there a load event to the database itself?
>>> >>
>>> >
>>> >
>>>
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: security only works on my PC
    ... still able to enter Explorer and enter the database without a login. ... checked the permissions box and the Users group has no permissions on ... Open it using your shortcut and log in. ... Click on the Groups option and select the Users Group. ...
    (microsoft.public.access.security)
  • Re: Security without signon
    ... >have not split my database and at this point would prefer not to. ... >have set up the form to run off a RWOP query, and I have removed all access ... >to the tables from the Users Group. ... give limited permissions to the Users group. ...
    (microsoft.public.access.security)
  • Re: security only works on my PC
    ... I checked the permissions box and the Users group has no ... Open/Run and open exclusive on database object ... Open it using your shortcut and log in. ... Click on the Groups option and select the Users Group. ...
    (microsoft.public.access.security)
  • Dual Workgroup - Problem with creating administrators
    ... It works and I can log on to the application using this second workgroup file. ... All permissions to the database have been revoked for the Users group and the ... are not administrators) and they could successfully log on to the application. ...
    (microsoft.public.access.security)
  • Re: Trying to program workgroup security using DAO... Help!!
    ... After you created a new workgroup file, you then created a new user to be a member of Admins. ... Here are the steps I've taken to secure a target database (which is ... Assigning permissions. ... Assigned all specific permissions to objects for the new groups I ...
    (microsoft.public.access.security)
Loading