Secure multiuser applications w/out securing existing/new database

[Guest]

My database is secure and password protected giving different access to
different groups. I've created a new .mdw file in conjunction with this.
I've joined this database with the new .mdw file. What I would like to do is
to find a way to run this secured database without affecting the existing or
new databases with this security. I understand the concept of joining a .mdw
file and if it were just me, I could manage that. But, this database needs
to be accessed by individuals who aren't as computer literate and I need to
make this as user-friendly as I can. I've thought of creating a macro at the
onset joining the database to the secure .mdw and then another macro at the
end of the session joining the database to the unsecured .mdw. However,
during a session, if someone created a database, it would be joined to the
secured .mdw. What can I do?

 

[Rick Brandt]

My database is secure and password protected giving different access
to different groups. I've created a new .mdw file in conjunction
with this. I've joined this database with the new .mdw file. What I
would like to do is to find a way to run this secured database
without affecting the existing or new databases with this security.
I understand the concept of joining a .mdw file and if it were just
me, I could manage that. But, this database needs to be accessed by
individuals who aren't as computer literate and I need to make this
as user-friendly as I can. I've thought of creating a macro at the
onset joining the database to the secure .mdw and then another macro
at the end of the session joining the database to the unsecured .mdw.
However, during a session, if someone created a database, it would be
joined to the secured .mdw. What can I do?

You cannot do this at all from the secured MDB. The SESSION is what uses a
particular MDW and that happens before the MDB is opened. By the time you
run code or macro it is too late.

You can create a shortcut for your users that specifies the secured MDW file
when opening the secured MDB. That way you leave their default workgroup
alone and things work normally for non-secured apps. The target for such a
shortcut would have the format...

"full path to MSAccess.exe" /wrkgrp "full path to MDW" "full path to MDB"

 

[Joan Wild]

Leave your computer joined by default to the standard system.mdw that ships
with Access. The common approach is to create a desktop shortcut to launch
your secure mdb. All other sessions will use the default. The shortcut
target would have the following, adjusted to suit the actual pathnames...
"path to msaccess.exe" "path to secure.mdb" /wrkgrp "path to secure mdw"