|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
workgroup information file (WIF) problemI created a database on my local drive and secured it using the wizard. I
then placed a copy/shortcut on a different drive. No one can open it but me. They all get an error message that they don't have permission... How do I change the current WIF to point to the new drive and not my local drive? Thanks a million. chouetteray wrote:
> I created a database on my local drive and secured it using the Copy/shortcut of what? Did you copy the WIF to a network location that all > wizard. I then placed a copy/shortcut on a different drive. users have permissions to? Did you copy the MDB to a network location that all users have permissions to? Did you copy the shortcut the wizard created to each user's PC? >No one Copying the shortcut to each user's PC will work, provided they have Access > can open it but me. They all get an error message that they don't > have permission... How do I change the current WIF to point to the > new drive and not my local drive? Thanks a million. installed in the same location as you do on your computer. The shortcut should look like: "path to msaccess.exe" "path to mdb" /wrkgrp "path to secure.mdw" You can use UNC pathnames for the mdb and mdw (\\server\share\ rather than some mapped drive letter). If you get the above working, you should split the database and leave the backend (tables/relationships) on the server. Give each user a copy of the frontend (all other objects with linked tables pointing to the backend on the server) on their PC. Then modify the "path to mdb" portion of the shortcut to point to the local copy of the frontend.mdb. When you split it, don't use the splitter wizard as that will result in an unsecure backend mdb. Instead split it manually. -- Joan Wild Microsoft Access MVP Hi Joan,
Can you point me to a reference which explains how to manually split a db. I have used the wizard previously but didn't realise that a manual split preserves back-end security. Thanks very mcuh, Ian. Show quoteHide quote "Joan Wild" wrote: > > chouetteray wrote: > > I created a database on my local drive and secured it using the > > wizard. I then placed a copy/shortcut on a different drive. > > Copy/shortcut of what? Did you copy the WIF to a network location that all > users have permissions to? Did you copy the MDB to a network location that > all users have permissions to? Did you copy the shortcut the wizard created > to each user's PC? > > > >No one > > can open it but me. They all get an error message that they don't > > have permission... How do I change the current WIF to point to the > > new drive and not my local drive? Thanks a million. > > Copying the shortcut to each user's PC will work, provided they have Access > installed in the same location as you do on your computer. > > The shortcut should look like: > "path to msaccess.exe" "path to mdb" /wrkgrp "path to secure.mdw" > > You can use UNC pathnames for the mdb and mdw > (\\server\share\ rather than some mapped drive letter). > > If you get the above working, you should split the database and leave the > backend (tables/relationships) on the server. Give each user a copy of the > frontend (all other objects with linked tables pointing to the backend on > the server) on their PC. Then modify the "path to mdb" portion of the > shortcut to point to the local copy of the frontend.mdb. > > When you split it, don't use the splitter wizard as that will result in an > unsecure backend mdb. Instead split it manually. > > > -- > Joan Wild > Microsoft Access MVP > > >
http://www.jmwild.com/SplitSecure.htm
--
Show quote
Hide quote
Joan Wild Microsoft Access MVP Ian wrote: > Hi Joan,
> > Can you point me to a reference which explains how to manually split > a db. I have used the wizard previously but didn't realise that a > manual split preserves back-end security. > > Thanks very mcuh, > Ian. > > "Joan Wild" wrote: > >> >> chouetteray wrote: >>> I created a database on my local drive and secured it using the >>> wizard. I then placed a copy/shortcut on a different drive. >> >> Copy/shortcut of what? Did you copy the WIF to a network location >> that all users have permissions to? Did you copy the MDB to a >> network location that all users have permissions to? Did you copy >> the shortcut the wizard created to each user's PC? >> >> >>> No one >>> can open it but me. They all get an error message that they don't >>> have permission... How do I change the current WIF to point to the >>> new drive and not my local drive? Thanks a million. >> >> Copying the shortcut to each user's PC will work, provided they have >> Access installed in the same location as you do on your computer. >> >> The shortcut should look like: >> "path to msaccess.exe" "path to mdb" /wrkgrp "path to secure.mdw" >> >> You can use UNC pathnames for the mdb and mdw >> (\\server\share\ rather than some mapped drive letter). >> >> If you get the above working, you should split the database and >> leave the backend (tables/relationships) on the server. Give each >> user a copy of the frontend (all other objects with linked tables >> pointing to the backend on the server) on their PC. Then modify the >> "path to mdb" portion of the shortcut to point to the local copy of >> the frontend.mdb. >> >> When you split it, don't use the splitter wizard as that will result >> in an unsecure backend mdb. Instead split it manually. >> >> >> -- >> Joan Wild >> Microsoft Access MVP
How Do I Prevent Access 2003 Crash when using Digital ID & Library
User level security 2002 / 2003 Unsecuring a secure Access Database? Permissions Help Design Master security digital signature trouble Providing logins for users and filtering records based on users Backend DB Password access security Is there a way to set up an audit tracking in Access? |
|||||||||||||||||||||||