G
Guest
How do I create security to a single database on a network without effecting
other databases on the same network?
other databases on the same network?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
R
Rick B
If you follow all the steps in the security white pages, you will be
creating a new workgroup file and securing a particular database to that
workgroup. Your users would still be using the default (unchanged)
workgroup file for all their other databases.
In short, if you follow the proper procedures, you will not affect anything
except the database file you wish to secure.
creating a new workgroup file and securing a particular database to that
workgroup. Your users would still be using the default (unchanged)
workgroup file for all their other databases.
In short, if you follow the proper procedures, you will not affect anything
except the database file you wish to secure.
G
Guest
I need more detail. I tried reading the help files. I thought I set-up
everything like it tells me but somehow there is a logon promt for every
database that my users try to open. Should my users "join" the workgroup or
is that wrong? Thats what I did and that is what seems to be the problem but
when I join the orginal security file then they are unable to open the
database that I have created. I need lots of help!
everything like it tells me but somehow there is a logon promt for every
database that my users try to open. Should my users "join" the workgroup or
is that wrong? Thats what I did and that is what seems to be the problem but
when I join the orginal security file then they are unable to open the
database that I have created. I need lots of help!
R
Rick B
No, they should not join your secure workgroup. They should remain joined
to the SYSTEM.MDW file. You should create a shortcut to your secure
database that includes the MDW file that should be used in the path.
I would join the default workgroup and then try to open the secured
database. If you secured it properly, it will not let you open the file.
Very often when steps are missed, you WILL be able to open it. If that
happens, then your file is not secured. A user could open it with their
default workgroup.
Security FAQ
http://support.microsoft.com/?id=207793
The Security Whitepaper is also worth reading to help you understand.
http://support.microsoft.com/?id=148555
Joan Wild:
www.jmwild.com/AccessSecurity.htm
Lynn Trapp
http://www.ltcomputerdesigns.com/Security.htm
to the SYSTEM.MDW file. You should create a shortcut to your secure
database that includes the MDW file that should be used in the path.
I would join the default workgroup and then try to open the secured
database. If you secured it properly, it will not let you open the file.
Very often when steps are missed, you WILL be able to open it. If that
happens, then your file is not secured. A user could open it with their
default workgroup.
Security FAQ
http://support.microsoft.com/?id=207793
The Security Whitepaper is also worth reading to help you understand.
http://support.microsoft.com/?id=148555
Joan Wild:
www.jmwild.com/AccessSecurity.htm
Lynn Trapp
http://www.ltcomputerdesigns.com/Security.htm
I
Immanuel Sibero
Patrick,
Well, here's the detail:
http://www.jmwild.com/Accesssecurity.htm
Access security is rather complex and not for the faint of heart (as you
might have found out). The Help file is definitely inadequate. One should
not even try to implement Access security on a production system without
first consulting the above information. I would also recommend practicing
the steps above on a 'copy' of your database, and practice multiple times.
HTH,
Immanuel Sibero
I need more detail. I tried reading the help files. I thought I set-up
Well, here's the detail:
http://www.jmwild.com/Accesssecurity.htm
Access security is rather complex and not for the faint of heart (as you
might have found out). The Help file is definitely inadequate. One should
not even try to implement Access security on a production system without
first consulting the above information. I would also recommend practicing
the steps above on a 'copy' of your database, and practice multiple times.
HTH,
Immanuel Sibero
J
Joan Wild
Since they can't open your secure mdb while joined to the system.mdw, that's
a good sign that you secured it properly. Leave them joined to system.mdw
and provide a desktop shortcut for your secure mdb.
All sessions will default to using system.mdw. When they use the desktop
shortcut, the default mdw is over-ridden and your secure mdw is used. The
target of the shortcut would look like:
"path to msaccess.exe" "path to mdb" /wrkgrp "path to secure mdw"
a good sign that you secured it properly. Leave them joined to system.mdw
and provide a desktop shortcut for your secure mdb.
All sessions will default to using system.mdw. When they use the desktop
shortcut, the default mdw is over-ridden and your secure mdw is used. The
target of the shortcut would look like:
"path to msaccess.exe" "path to mdb" /wrkgrp "path to secure mdw"