Re: Security not clicking

Thanks alot Joan for this info.
I have followed the right procedure but now it is taking time before
the report prints.
I have been waiting for almost 1 hour for it to complete enhancing
security..(is this normal?). I restarted the whole process and deleted
the other .mdw files I had created earlier.
I hope I can finish it soon.
Billy
Joan Wild wrote:
You do not create a shortcut on the network.

1. Copy the backend to the server (you've done this).
2. Copy the secure mdw to the server(you've done this).
However you said the mdw needed you to import data. Can you describe
exactly the messages you received. There is no need to import or do
anything to the mdw.
Mdw did not show all users as per one-step security wizard report. I
believe you said you had multiple mdw files and so likely there is a mix of
which one should be used. I suggest you revert to your unsecured database
and start over. You need only one secure mdw. Once you have it done, it's
that mdw that goes on the server. And it *will* contain all the users you
need.

Is your database split right now?
Yes - Good put the backend on the server. Open the frontend on your PC, and
use Tools, Linked Table Manager, and refresh the links; be sure to put a
check at the bottom to prompt for location and choose the location of the
backend on the server.
No - Split the database. See www.jmwild.com/SplitSecure.htm for steps. Put
the backend on the server and refresh the links as per the above.

If the wizard created a desktop shortcut for you on your PC, right-click it
and choose properties. It'll open to the Shortcut tab and the Target line
will be selected. The target will take the form similar to:
"path to msaccess.exe" "path to secure mdb" /wrkgrp "path to secure mdw"
secure mdb will be the original database on your PC - modify it (if
necessary) to reflect the path to the frontend on your c: drive.
path to secure mdw will be the secure mdw you used to secure your mdb
(somewhere on your C: drive) - change the path to reflect the location of
the secure mdw on the server.

Now, you'll have the backend and secure mdw on the server, a copy of the
frontend on your PC, and a shortcut on your desktop.

To set up other users you can just copy the frontend from your PC to them.
In addition you can copy the shortcut from your desktop to them (a shortcut
is just a file with a lnk extension). Ensure that you put the frontend in
the same location on their PC as it is in your's OR if you put it in a
different location, then modify the shortcut on *their* PC to reflect the
location of the frontend i.e. the target would look like:
"path to msaccess.exe" "path to frontend" /wrkgrp "path to secure mdw on
server"
and example:
"C:\Program Files\Microsoft Office\Office11\msaccess.exe"
"c:\MyApp\frontend.mdb" /wrkgrp "F:\databasefiles\secure.mdw"

Just another little wrinkle, but you can use the UNC pathname for the mdw;
i.e. \\servername\path\secure.mdw rather than 'F:' drive; this way you don't
have to worry about someone having a different drive mapping than you.


--
Joan Wild
Microsoft Access MVP

Billy wrote:
Joan,
Your help is great, but would you please provide step by step process
of creating a shortcut on the network as well as securing the backend
and/or frontend.
The secured database is seated on my desktop. I copied it to a folder
in the network..successful, I also copied the mdw file to the same
folder....successful, however, I realised that the mdw file needed me
to import data..(is this normal?). At the same time, the mdw did not
show everybody shown on the one-step security wizard report...(is this
also normal?). If you have some links like the one you sent
yesterday, I would appreciate. I have to admit that it is the first
time I am securing a database on my own.
Thanks for your help so far.
Billy
Joan Wild wrote:
You need to copy the secure mdw and the mdb to a folder on the
server that everyone has access to. All users will need
read/write/create/delete windows permissions on that folder.

You can give each user a desktop shortcut the uses the secure mdw
and opens the secure mdb. The target would look like:
"path to msaccess.exe" "path to secure mdb" /wrkgrp "path to secure
mdw"

It is highly recommended that you split the database. Put the
backend (tables/relationships only) mdb on the server. A copy of
the frontend (all other objects, and table links to the backend) mdb
would go on each user's computer. You'd modify the shortcut above
so that the path to secure mdb would be the path to the frontend.

If everyone has Access installed in the same folder, and the
frontend is installed in the same location on each PC, you can copy
the shortcut to each person.

Since you've secured it, you shouldn't use the database splitter
wizard, as that will result in an unsecure backend mdb. Instead
split it manually.

See www.jmwild.com/SplitSecure.htm



--
Joan Wild
Microsoft Access MVP

Billy wrote:
Everything seems to be going well at this point! Now how do I
distribute the database to the network or rather how do I create a
shortcut that can be accessed by everybody on the common drive?
Billy

.

Relevant Pages

  • Re: Security not clicking
    ... You do not create a shortcut on the network. ... Copy the backend to the server. ... Copy the secure mdw to the server. ...
    (microsoft.public.access.security)
  • Re: Security not clicking
    ... get an mdw file that is located on my desk top. ... Copy the secure mdw to the server. ... If the wizard created a desktop shortcut for you on your PC, ...
    (microsoft.public.access.security)
  • Re: Security not clicking
    ... unsecure mdb. ... I get an mdw file that is located on my desk top. ... Copy the secure mdw to the server. ... If the wizard created a desktop shortcut for you on your PC, ...
    (microsoft.public.access.security)
  • Re: Security not clicking
    ... Did you start with the original unsecured copy of your database? ... Did you compile and compact the mdb before running the wizard? ... Copy the secure mdw to the server. ...
    (microsoft.public.access.security)
  • RE: Workgroup Security
    ... I am going to make an .mde out of this database. ... Did you set an Admin Password in your new mdw? ... When you launch the shortcut does it ask you to authenticate with your ... use it for that mdb. ...
    (microsoft.public.access.security)