Security

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Having created a secured database and now have all the relevant passwords
etc, it created a shortcut which i now run from.
However, I need to distribute this file on to a shared drive and i cannot
find the main file and can only run off the shortcut.
ANy ideas?
 
Right-click the shortcut and check the line in the target box. It'll have
"path to msaccess.exe" "path to mdb" /wrkgrp "path to secure.mdw"

Just copy the mdb and the mdw from the paths indicated to the shared drive.

You'll need to modify your shortcut, changing the paths to reflect the new
location of the files. Then you'll need to provide your users with a
similar shortcut (it may differ slightly if users have a different path to
msaccess.exe than you do).

Having said that, you should consider splitting the mdb. Put just the
backend on the server, and give each user a copy of the frontend on their
computer. The shortcut would then be changed to
"path to msaccess.exe" "path to frontend on local machine" /wrkgrp "path to
secure mdw on server"

If you split the secure mdb, don't use the splitter wizard. See
www.jmwild.com/splitsecure.htm
 
Joan,
Thank you. However, i have already split the database using the wizard.
Will this make a difference?
Matt
 
I also have a problem, in that I split the database and was then told i had
to add more tables and didnt then do it in the backend! so I have two backend
tables
Is this a problem?
 
Did you use the wizard before or after you secured? If after, then you need
to resecure the backend. Just open the frontend using your shortcut, then
open the backend and proceed to secure it.

If before, then you're fine.

You need to copy the backend and the mdw to the server; your desktop
shortcut should be fine. Just copy the FE to each user.
 
Did you add these new tables to the frontend, or a completely separate mdb?

In any case, open the backend and use File, Import and import these tables
into the backend. You'll need to then set permissions on these tables, as
they don't travel with the import.
 
Back
Top