Home All Groups Group Topic Archive Search About

secured and unsecured dbase on pc

Author
13 Mar 2007 6:26 PM
Todd
I've got a secured database on my pc and I've also got another database on my
pc that should be unsecured but when I joined the workgroup to secure the
secured dbase it also defaulted the other dbase to prompt for user/password. 
How can I keep the security on the secured dbase while removing the unsecured
dbase workgroup file?
--
Todd

Author
15 Mar 2007 5:43 PM
Joan Wild
Access always uses a mdw file.  Keep your computer joined by default to the
standard system.mdw that ships with Access.  Create a desktop shortcut for
your secure mdb - use the shortcut to open the secure mdb.  All other
sessions will use the system.mdw and require no login.

The target of the shortcut would be
"path to msaccess.exe" "path to secure mdb" /wrkgrp "path to secure .mdw"


--
Joan Wild
Microsoft Access MVP
Show quoteHide quote
"Todd" <t**@discussions.microsoft.com> wrote in message
news:076DCC0E-ABE1-4FCC-AF58-0EC6BCA378DF@microsoft.com...
> I've got a secured database on my pc and I've also got another database on
> my
> pc that should be unsecured but when I joined the workgroup to secure the
> secured dbase it also defaulted the other dbase to prompt for
> user/password.
> How can I keep the security on the secured dbase while removing the
> unsecured
> dbase workgroup file?
> --
> Todd
Author
20 Mar 2007 2:24 PM
Todd
It's me again.  Here is the path I included in the shortcut on my desktop
(I'm running Access 2003):

"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" C:\Documents and
Settings\All Users\Application Data\Vehicle Database\mgcvdb.3.13.07.exe.mde"
/wrkgrp "\\Mgcjaxnn\Vehicle Database\vehiclesecurity.mdw"

First part is where MSACCESS.EXE is on my pc.
Second part is where I'll store the executable on each persons pc (and mine).
Third part is where the security file is on the server.

I' getting an error message that says:

"The Command line you used to start Microsoft Office Access contains an
option that Microsoft Office Access doesn't recognize"

--
Todd


Show quoteHide quote
"Joan Wild" wrote:

> Access always uses a mdw file.  Keep your computer joined by default to the
> standard system.mdw that ships with Access.  Create a desktop shortcut for
> your secure mdb - use the shortcut to open the secure mdb.  All other
> sessions will use the system.mdw and require no login.
>
> The target of the shortcut would be
> "path to msaccess.exe" "path to secure mdb" /wrkgrp "path to secure .mdw"
>
>
> --
> Joan Wild
> Microsoft Access MVP
> "Todd" <t**@discussions.microsoft.com> wrote in message
> news:076DCC0E-ABE1-4FCC-AF58-0EC6BCA378DF@microsoft.com...
> > I've got a secured database on my pc and I've also got another database on
> > my
> > pc that should be unsecured but when I joined the workgroup to secure the
> > secured dbase it also defaulted the other dbase to prompt for
> > user/password.
> > How can I keep the security on the secured dbase while removing the
> > unsecured
> > dbase workgroup file?
> > --
> > Todd
>
>
>
Author
20 Mar 2007 2:27 PM
Todd
Never mind. I apparently forgot a " before the C:\Documents and Settings.
--
Todd


Show quoteHide quote
"Joan Wild" wrote:

> Access always uses a mdw file.  Keep your computer joined by default to the
> standard system.mdw that ships with Access.  Create a desktop shortcut for
> your secure mdb - use the shortcut to open the secure mdb.  All other
> sessions will use the system.mdw and require no login.
>
> The target of the shortcut would be
> "path to msaccess.exe" "path to secure mdb" /wrkgrp "path to secure .mdw"
>
>
> --
> Joan Wild
> Microsoft Access MVP
> "Todd" <t**@discussions.microsoft.com> wrote in message
> news:076DCC0E-ABE1-4FCC-AF58-0EC6BCA378DF@microsoft.com...
> > I've got a secured database on my pc and I've also got another database on
> > my
> > pc that should be unsecured but when I joined the workgroup to secure the
> > secured dbase it also defaulted the other dbase to prompt for
> > user/password.
> > How can I keep the security on the secured dbase while removing the
> > unsecured
> > dbase workgroup file?
> > --
> > Todd
>
>
>