G
Guest
When opening the shortcut, security works fine. When opening the main .mdb it
opens without security. Well if people learn the path won't they be able to
open the original file and see everything? If I have the original .mdb put in
a network folder that is inaccessible to them, will they be able to view the
information in the database via shortcut?
-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"
opens without security. Well if people learn the path won't they be able to
open the original file and see everything? If I have the original .mdb put in
a network folder that is inaccessible to them, will they be able to view the
information in the database via shortcut?
-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"