"Scott McDaniel" wrote:

> On 11 Jul 2006 09:28:39 -0700, PadmaBhas***@gmail.com wrote:
>
> >I have a MS Access application which would be on the network and
> >multiple users must be able to access using their respective used ids.
> >I wanted to create user ids and grant permissions based on user ids.
> >First, I created a workgroup using Tools -> Security -> Workgroup
> >Adminstrator. I created user accounts and set permission level to
> >tables, queries etc.
> >
> >Now, the issue is when I try to open some other MS Access application/
> >MDB file, it asks for the user name, passowrd. All the security
> >settings seem to be done at a global level on my computer.
>
> You've "joined" your workgroup file on your machine, and obviously the Admin user has a non-blank password, which is why
> all Access apps are prompting for login. Find and rejoin your default System.mdw file and the login prompts should stop.
>
> >The other
> >problem is, when I access my application from a different computer, it
> >does not ask for any user id, password. So, the database is not
> >ultimately not secure.
> >
>
> You've not properly secured your database if that's the case. With a properly secured database, you would get the
> standard "You don't have permissions blah blah" message. I'd strongly encourage you to read up on the proper application
> of User Level Security before mucking around with it too much more. Also, make sure to experiment on a COPY of your
> database (best to keep a good copy off-machine, on a network drive or USB stick).
>
> When you do finally get your db correctly secured, you'll need to place your workgroup file on a network-accessible
> drive/folder, and "point" your users to it. This is usually done with a shortcut on the user's desktop, the Target of
> which is something like this:
>
> "Full path to MSAccess.exe" "Full path to your db" /wrkgrp "Full path to the workgroup file"
>
> The MS Access Security FAQ:
> http://support.microsoft.com/default.aspx?scid=%2Fsupport%2Faccess%2Fcontent%2Fsecfaq.asp
>
> Joan Wild's page, with instructions on how to properly secure a database without the Security Wizard:
> http://www.jmwild.com/Accesssecurity.htm
>
> Lynn Trapp's page, with more info on security:
> http://www.ltcomputerdesigns.com/Security.htm
>
> Jack MacDonald has a great paper explaining what ULS is and how it works
> http://www.geocities.com/jacksonmacd/
>
> Scott McDaniel
> scott@takemeout_infotrakker.com
> www.infotrakker.com
>

> Scott,
>
> I have the same problem I believe, but the link is not working, do
> you have another with the same subject somewhere?
>
> "Scott McDaniel" wrote:
>
>> On 11 Jul 2006 09:28:39 -0700, PadmaBhas***@gmail.com wrote:
>>
>>> I have a MS Access application which would be on the network and
>>> multiple users must be able to access using their respective used
>>> ids. I wanted to create user ids and grant permissions based on
>>> user ids. First, I created a workgroup using Tools -> Security ->
>>> Workgroup Adminstrator. I created user accounts and set permission
>>> level to tables, queries etc.
>>>
>>> Now, the issue is when I try to open some other MS Access
>>> application/ MDB file, it asks for the user name, passowrd. All the
>>> security settings seem to be done at a global level on my computer.
>>
>> You've "joined" your workgroup file on your machine, and obviously
>> the Admin user has a non-blank password, which is why all Access
>> apps are prompting for login. Find and rejoin your default
>> System.mdw file and the login prompts should stop.
>>
>>> The other
>>> problem is, when I access my application from a different computer,
>>> it does not ask for any user id, password. So, the database is not
>>> ultimately not secure.
>>>
>>
>> You've not properly secured your database if that's the case. With a
>> properly secured database, you would get the standard "You don't
>> have permissions blah blah" message. I'd strongly encourage you to
>> read up on the proper application of User Level Security before
>> mucking around with it too much more. Also, make sure to experiment
>> on a COPY of your database (best to keep a good copy off-machine, on
>> a network drive or USB stick).
>>
>> When you do finally get your db correctly secured, you'll need to
>> place your workgroup file on a network-accessible drive/folder, and
>> "point" your users to it. This is usually done with a shortcut on
>> the user's desktop, the Target of which is something like this:
>>
>> "Full path to MSAccess.exe" "Full path to your db" /wrkgrp "Full
>> path to the workgroup file"
>>
>> The MS Access Security FAQ:
>> http://support.microsoft.com/default.aspx?scid=%2Fsupport%2Faccess%2Fcontent%2Fsecfaq.asp
>>
>> Joan Wild's page, with instructions on how to properly secure a
>> database without the Security Wizard:
>> http://www.jmwild.com/Accesssecurity.htm
>>
>> Lynn Trapp's page, with more info on security:
>> http://www.ltcomputerdesigns.com/Security.htm
>>
>> Jack MacDonald has a great paper explaining what ULS is and how it
>> works
>> http://www.geocities.com/jacksonmacd/
>>
>> Scott McDaniel
>> scott@takemeout_infotrakker.com
>> www.infotrakker.com

"Joan Wild" wrote:

> MS recently removed Scott's link.  Try
>  http://support.microsoft.com/?id=207793
>
> --
> Joan Wild
> Microsoft Access MVP
>
> Sal wrote:
> > Scott,
> >
> > I have the same problem I believe, but the link is not working, do
> > you have another with the same subject somewhere?
> >
> > "Scott McDaniel" wrote:
> >
> >> On 11 Jul 2006 09:28:39 -0700, PadmaBhas***@gmail.com wrote:
> >>
> >>> I have a MS Access application which would be on the network and
> >>> multiple users must be able to access using their respective used
> >>> ids. I wanted to create user ids and grant permissions based on
> >>> user ids. First, I created a workgroup using Tools -> Security ->
> >>> Workgroup Adminstrator. I created user accounts and set permission
> >>> level to tables, queries etc.
> >>>
> >>> Now, the issue is when I try to open some other MS Access
> >>> application/ MDB file, it asks for the user name, passowrd. All the
> >>> security settings seem to be done at a global level on my computer.
> >>
> >> You've "joined" your workgroup file on your machine, and obviously
> >> the Admin user has a non-blank password, which is why all Access
> >> apps are prompting for login. Find and rejoin your default
> >> System.mdw file and the login prompts should stop.
> >>
> >>> The other
> >>> problem is, when I access my application from a different computer,
> >>> it does not ask for any user id, password. So, the database is not
> >>> ultimately not secure.
> >>>
> >>
> >> You've not properly secured your database if that's the case. With a
> >> properly secured database, you would get the standard "You don't
> >> have permissions blah blah" message. I'd strongly encourage you to
> >> read up on the proper application of User Level Security before
> >> mucking around with it too much more. Also, make sure to experiment
> >> on a COPY of your database (best to keep a good copy off-machine, on
> >> a network drive or USB stick).
> >>
> >> When you do finally get your db correctly secured, you'll need to
> >> place your workgroup file on a network-accessible drive/folder, and
> >> "point" your users to it. This is usually done with a shortcut on
> >> the user's desktop, the Target of which is something like this:
> >>
> >> "Full path to MSAccess.exe" "Full path to your db" /wrkgrp "Full
> >> path to the workgroup file"
> >>
> >> The MS Access Security FAQ:
> >> http://support.microsoft.com/default.aspx?scid=%2Fsupport%2Faccess%2Fcontent%2Fsecfaq.asp
> >>
> >> Joan Wild's page, with instructions on how to properly secure a
> >> database without the Security Wizard:
> >> http://www.jmwild.com/Accesssecurity.htm
> >>
> >> Lynn Trapp's page, with more info on security:
> >> http://www.ltcomputerdesigns.com/Security.htm
> >>
> >> Jack MacDonald has a great paper explaining what ULS is and how it
> >> works
> >> http://www.geocities.com/jacksonmacd/
> >>
> >> Scott McDaniel
> >> scott@takemeout_infotrakker.com
> >> www.infotrakker.com
>
>
>