> This is a fairly remedial question. I need to create user-level
> security on a database that exists on a network. I have only two
> groups- those who can modify the database and those who cannot. While
> I have successfully used the the security wizard to create a secure
> database, I cannot seem to open the network-based database from any
> computer other than the one where I created the security levels. I
> have not found my problem addressed on the Microsoft support website.
> What am I doing wrong? Any advisement on this matter is appreciated.

"Joan Wild" wrote:

> What version of Access?  There's more to securing a database than running
> the wizard.
>
> --
> Joan Wild
> Microsoft Access MVP
>
> jss wrote:
> > This is a fairly remedial question. I need to create user-level
> > security on a database that exists on a network. I have only two
> > groups- those who can modify the database and those who cannot. While
> > I have successfully used the the security wizard to create a secure
> > database, I cannot seem to open the network-based database from any
> > computer other than the one where I created the security levels. I
> > have not found my problem addressed on the Microsoft support website.
> > What am I doing wrong? Any advisement on this matter is appreciated.
>
>
>

> I am using Access 2003.
>
> "Joan Wild" wrote:
>
>> What version of Access?  There's more to securing a database than
>> running the wizard.
>>
>> --
>> Joan Wild
>> Microsoft Access MVP
>>
>> jss wrote:
>>> This is a fairly remedial question. I need to create user-level
>>> security on a database that exists on a network. I have only two
>>> groups- those who can modify the database and those who cannot.
>>> While I have successfully used the the security wizard to create a
>>> secure database, I cannot seem to open the network-based database
>>> from any computer other than the one where I created the security
>>> levels. I have not found my problem addressed on the Microsoft
>>> support website. What am I doing wrong? Any advisement on this
>>> matter is appreciated.

"Joan Wild" wrote:

> You need to make the mdw that was created, available to other computers.
> Put it in the same folder as the backend mdb.  Then give each user a desktop
> shortcut.  The wizard made one for you.  As long as everyone has a typical
> install of Access, you should be able to just copy your shortcut to them.
>
> --
> Joan Wild
> Microsoft Access MVP
>
> jss wrote:
> > I am using Access 2003.
> >
> > "Joan Wild" wrote:
> >
> >> What version of Access?  There's more to securing a database than
> >> running the wizard.
> >>
> >> --
> >> Joan Wild
> >> Microsoft Access MVP
> >>
> >> jss wrote:
> >>> This is a fairly remedial question. I need to create user-level
> >>> security on a database that exists on a network. I have only two
> >>> groups- those who can modify the database and those who cannot.
> >>> While I have successfully used the the security wizard to create a
> >>> secure database, I cannot seem to open the network-based database
> >>> from any computer other than the one where I created the security
> >>> levels. I have not found my problem addressed on the Microsoft
> >>> support website. What am I doing wrong? Any advisement on this
> >>> matter is appreciated.
>
>
>

>I'm still not having any luck. The security mdw was created in the same
>folder (the networked one) as the backend mdb. I tried pasting the shortcut
>in the network folder and then putting it on the desktop of the other
>computers. When I try and open the file on the other computers, I get an
>error message that I don't have the necessary permissions. Also, I just
>realized that I am working between Access 2003 on the computer I used to
>secure the database and Access 2002 on the computer I am testing it on. Could
>this be the problem?   
>
>I apologize for a complete lack of familiarity with this area of Access.
>Although I've used it for years, I've never used any of its security
>functions. Thanks for the help.
>
>> You need to make the mdw that was created, available to other computers.
>> Put it in the same folder as the backend mdb.  Then give each user a desktop
>[quoted text clipped - 19 lines]
>> >>> support website. What am I doing wrong? Any advisement on this
>> >>> matter is appreciated.

"Jeff O via AccessMonster.com" wrote:

> jss,  when you say the db won't open up. are you saying that the security you
> created using the wizard is not stoppting and asking for a login, or are you
> getting the login screen and you can't get past there because the password
> isn't accepting!. 
>
> I would be sure that your pointing to the correct mdw.  check the db by
> bypassing the security.  Hold down the shift key and you can go right into
> the db.  check tools > security > workgroup admin and be sure your pointing
> to the common system.mdw.  then be sure you shortcut points with the
> appropriate argument "
> should look something like this:
> "C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "s:\stars_dev.mdb"
> /wrkgrp "s:\dev_security.mdw"
>
> Hope that gives some additional help.  Security can be a pain (-:
>
> /Jeff
>
>
> jss wrote:
> >I'm still not having any luck. The security mdw was created in the same
> >folder (the networked one) as the backend mdb. I tried pasting the shortcut
> >in the network folder and then putting it on the desktop of the other
> >computers. When I try and open the file on the other computers, I get an
> >error message that I don't have the necessary permissions. Also, I just
> >realized that I am working between Access 2003 on the computer I used to
> >secure the database and Access 2002 on the computer I am testing it on. Could
> >this be the problem?   
> >
> >I apologize for a complete lack of familiarity with this area of Access.
> >Although I've used it for years, I've never used any of its security
> >functions. Thanks for the help.
> >
> >> You need to make the mdw that was created, available to other computers.
> >> Put it in the same folder as the backend mdb.  Then give each user a desktop
> >[quoted text clipped - 19 lines]
> >> >>> support website. What am I doing wrong? Any advisement on this
> >> >>> matter is appreciated.
>
>
> --
> Message posted via AccessMonster.com
> http://www.accessmonster.com/Uwe/Forums.aspx/access-security/200510/1
>

> I'm still not having any luck. The security mdw was created in the
> same folder (the networked one) as the backend mdb. I tried pasting
> the shortcut in the network folder and then putting it on the desktop
> of the other computers. When I try and open the file on the other
> computers, I get an error message that I don't have the necessary
> permissions. Also, I just realized that I am working between Access
> 2003 on the computer I used to secure the database and Access 2002 on
> the computer I am testing it on. Could this be the problem?
>
> I apologize for a complete lack of familiarity with this area of
> Access. Although I've used it for years, I've never used any of its
> security functions. Thanks for the help.
>
> "Joan Wild" wrote:
>
>> You need to make the mdw that was created, available to other
>> computers. Put it in the same folder as the backend mdb.  Then give
>> each user a desktop shortcut.  The wizard made one for you.  As long
>> as everyone has a typical install of Access, you should be able to
>> just copy your shortcut to them.
>>
>> --
>> Joan Wild
>> Microsoft Access MVP
>>
>> jss wrote:
>>> I am using Access 2003.
>>>
>>> "Joan Wild" wrote:
>>>
>>>> What version of Access?  There's more to securing a database than
>>>> running the wizard.
>>>>
>>>> --
>>>> Joan Wild
>>>> Microsoft Access MVP
>>>>
>>>> jss wrote:
>>>>> This is a fairly remedial question. I need to create user-level
>>>>> security on a database that exists on a network. I have only two
>>>>> groups- those who can modify the database and those who cannot.
>>>>> While I have successfully used the the security wizard to create a
>>>>> secure database, I cannot seem to open the network-based database
>>>>> from any computer other than the one where I created the security
>>>>> levels. I have not found my problem addressed on the Microsoft
>>>>> support website. What am I doing wrong? Any advisement on this
>>>>> matter is appreciated.

"Joan Wild" wrote:

> Please post what is in that shortcut (the target line).  Also what username
> are you trying to login as (On the other computers).
>
> Provide more specific details/errors please.
>
>
> --
> Joan Wild
> Microsoft Access MVP
>
> jss wrote:
> > I'm still not having any luck. The security mdw was created in the
> > same folder (the networked one) as the backend mdb. I tried pasting
> > the shortcut in the network folder and then putting it on the desktop
> > of the other computers. When I try and open the file on the other
> > computers, I get an error message that I don't have the necessary
> > permissions. Also, I just realized that I am working between Access
> > 2003 on the computer I used to secure the database and Access 2002 on
> > the computer I am testing it on. Could this be the problem?
> >
> > I apologize for a complete lack of familiarity with this area of
> > Access. Although I've used it for years, I've never used any of its
> > security functions. Thanks for the help.
> >
> > "Joan Wild" wrote:
> >
> >> You need to make the mdw that was created, available to other
> >> computers. Put it in the same folder as the backend mdb.  Then give
> >> each user a desktop shortcut.  The wizard made one for you.  As long
> >> as everyone has a typical install of Access, you should be able to
> >> just copy your shortcut to them.
> >>
> >> --
> >> Joan Wild
> >> Microsoft Access MVP
> >>
> >> jss wrote:
> >>> I am using Access 2003.
> >>>
> >>> "Joan Wild" wrote:
> >>>
> >>>> What version of Access?  There's more to securing a database than
> >>>> running the wizard.
> >>>>
> >>>> --
> >>>> Joan Wild
> >>>> Microsoft Access MVP
> >>>>
> >>>> jss wrote:
> >>>>> This is a fairly remedial question. I need to create user-level
> >>>>> security on a database that exists on a network. I have only two
> >>>>> groups- those who can modify the database and those who cannot.
> >>>>> While I have successfully used the the security wizard to create a
> >>>>> secure database, I cannot seem to open the network-based database
> >>>>> from any computer other than the one where I created the security
> >>>>> levels. I have not found my problem addressed on the Microsoft
> >>>>> support website. What am I doing wrong? Any advisement on this
> >>>>> matter is appreciated.
>
>
>

"Joan Wild" wrote:

> jss wrote:
> > The following is what my shortcuts targets:
> >
> > "\\Anthro84\c$\Program Files\Microsoft Office
> > 2003\OFFICE11\MSACCESS.EXE" "Z:\TONT PHOTOS Database.mdb" /WRKGRP
> > "Z:\Security.mdw"
>
> I would modify this target to
> "C:\Program Files\Microsoft Office 2003\Office11\msaccess.exe" ....
>
> Also, you are better off using UNC pathnames, rather than relying on users
> having the same drive mappings.  So \\servername\share\...
>
> You could work on getting this working and then consider....
> In addition, it is recommended that you split the database so that just the
> backend (tables only) sits on the server.  Give each user a copy of the
> frontend on their workstation (it would contain links to the backend).  Then
> your target would change to
> "path to msaccess.exe "c:\path to frontend" /wrkgrp
> "\\servername\share\...security.mdw"
>
> > In looking at the shortcut target above, however, I wonder if the
> > problem isn't that I am trying to open the mdw shortcut in Acess 2003
> > when I only have Access 2002 on the machines I am trying to open it
> > on. Do you think it would help if I went in and modified the target
> > on the computers with Access 2002 to reflect the 2002 status.
>
> Actually the security.mdw file isn't the problem here.  On the 2002
> machines, you will have to modify the path to msaccess.exe to reflect its
> location on that machine (do a search for it).  I'll guarantee it won't be
> beneath c:\Program Files\Microsoft office 2003
>
>  Also,
> > and I know this is very remedial, how do I go about making a new
> > shortcut to the mdw on the other computers.
>
> I would search for msaccess.exe on the computer (start, search).  Right
> click on it and 'send to desktop as shortcut'.  Then go to the desktop and
> right-click on the shortcut and choose properties.  You'll be on the target
> line and it will have the path to msaccess.exe there.  Edit that line as
> follows:
> Leave the path as is.
> Put double quotes around the path
> Move to the end of the line and type
> <space> "<Path to mdb>" <space> /wrkgrp <space> "<path to mdw>"
>
> --
> Joan Wild
> Microsoft Access MVP
>
>
>