Re: Shortcuts for other users

I would secure it and split it manually. As to permissions on the folder,
do you have IT support that can do this for you?

--
Joan Wild
Microsoft Access MVP
"Graeme at Raptup" <GraemeatRaptup@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:23CD4F3E-0939-44CA-89BF-BFC381151874@xxxxxxxxxxxxxxxx
Thanks Joan,
must i run the manual split before I run the user level security?
Or do I install the security without adding any users (and add the users
at
the end)?
I'm testing this out at home. What I did is deleted the secure database &
copied the original back to the working folder. Then I ran the manual
split
as per your website.
Looking at your instructions I now lack the secure.mdw so I'm not sure how
this will impact folders if I install security at this stage.
Also, not sure how to give users modify permissions on specific
folders....

Cheers,

Graeme

"Joan Wild" wrote:

"Graeme at Raptup" <GraemeatRaptup@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:577B7032-B975-4786-81A4-EC712FB1183B@xxxxxxxxxxxxxxxx
Also, I'd like to split the database. Is it a problem to split after
securing the database with the wizard?

You'll want to split it before setting up the any users.

You need to split it manually, as using the splitter wizard will result
in
an unsecured backend mdb. See www.jmwild.com/SplitSecure.htm
When you're done, you'll put the backend mdb and the secure mdw on the S:
drive. All users of the mdb will need modify permission on the folder
where
these files are located. You'll put a copy of the frontend mdb on each
user's computer and a shortcut on each desktop.

If you are certain that all users will have the s: drive mapped the same,
have Access installed in the same folder, and that they all have the
frontend installed to the same folder on their computer, you can simply
copy
the shortcut (it's just a file with a lnk extension) to each user.

If any of the above is different for any user, you'll need to modify the
shortcut to reflect the correct paths. With regard to the S: drive
mapping,
you can use UNC pathnames and then the users' drive mappings won't
matter.
To do this you'd use My Network Places to navigate to the backend table
when
you create these links. In addition, in the shortcut target you'd use
\\servername\share\path\ format for the path to the secure mdw.

--
Joan Wild
Microsoft Access MVP





.

Relevant Pages

  • Re: Help - locked out of database
    ... IT checked all the permissions and everything seems to be ok. ... "Joan Wild" wrote: ... I have poured a year into this database - is there someway to recover this? ... You need, at minimum, modify permission on the folder. ...
    (microsoft.public.access.security)
  • Microsoft Windows Vista/2003/XP/2000 file management security issues
    ... This is an article I promised to publish after Windows ... This article contains a set of attack scenarios to demonstrate security ... It's just something you believe is secure and it's not. ... inability to create secured file / folder in public one. ...
    (Bugtraq)
  • [Full-disclosure] Microsoft Windows Vista/2003/XP/2000 file management security issues
    ... This is an article I promised to publish after Windows ... This article contains a set of attack scenarios to demonstrate security ... It's just something you believe is secure and it's not. ... inability to create secured file / folder in public one. ...
    (Full-Disclosure)
  • Re: MS words
    ... Can anyone tell me how to secure a doc. ... it uses the superior method of explicitly assigning file/folder permissions to individual users ... HOW TO Set the My Documents Folder as Private in Windows XP ... Best Practices for Encrypting File System ...
    (microsoft.public.windowsxp.newusers)
  • Re: Only one user can log in at a time problem.
    ... > the mdw is in the Workgroup folder, ... > MQA Database folder. ... >>Joan Wild ... >>>>read, write, modify permissions to the folders. ...
    (microsoft.public.access.security)