Re: Securing the Front End database

Tech-Archive recommends: Speed Up your PC by fixing your registry

Hi Joan,

I really appreciate you for helping me. I think I am almost there. Please
help. This is what I have currently.

I changed the target of the shortcut to the string that you told me. Then I
sent it to the users. When the users click on it from their local drive, it
will prompt them for the login info. The shortcut is pointed to the same FE
on the shared drive. The only problem I see is when more than one user tries
to use, would it let them use since it pointed to the same FE?

As far as the actual FE and other databases, they have rejoined to the
generic System.mdw, so now they are not prompted for a login info. However,
when I click on the FE in Windows Explorer, it opens. I thought it should
not open? Am I missing something?

Again, Thanks very much. Please help.

"Joan Wild" wrote:

Open Access and go to Tools, Security, Workgroup Administrator.
It will tell you what your current default mdw file is. It should be
system.mdw (the one that ships with Access). It usually is located in the
windows system folder, but that depends on the Operating System. You could
search for it first - Start, Search.

If you are not already joined to this mdw, then click on Join and join it.

Now create a desktop shortcut. It will have the following in the target:
"path to msaccess.exe" "path to FE" /wrkgrp "path to Database Security.mdw"
You'll need to substitute the correct paths in the above.

When you need to make changes to this secure mdb, use the desktop shortcut
to open it. For all other non-secured mdb files, just open Access and it'll
use the standard system.mdw file.


--
Joan Wild
Microsoft Access MVP

AccessHelp wrote:
Joan,

Thanks. I have a few more questions.

1. Do I create a shortcut of my FE and join the shortcut FE to the
Database Security.mdw that I created? And I rejoin the actual FE to
the default System.mdw?
2. So if I do step 1, I will not able to open the actual FE.
Therefore, how do I make changes to the actual FE? Will it also lock
the BE?

I am confused. What I do is, I make changes to the FE from time to
time. Then I email the FE to the users for them to use. Now I am
trying to secure the database from unauthorized people get into the
database. If you would, please share with me step-by-step on
implementing the whole thing.

Thanks very much.

"Joan Wild" wrote:


AccessHelp wrote:

1. The database that I secure is linked to 3 other databases.
When I secure that database, the other 3 databases are
automatically secured too. Why, and how do I unsecure the other 3?

They are not secured. When you created a new workgroup file, Access
made it the default one to use in all sessions. The workgroup file
is tied to the session, not the database. Since your default mdw is
the secure mdw you used to secure database 1, and it is now the
default, you'll be prompted for username/password for every session
of Access.

Use the workgroup administrator to rejoin system.mdw. This is the
workgroup that ships with Access. Access always uses a workgroup
file, whether you implement security or not.

2. When I went thru the steps from the link that you gave me, I
didn't get the step 21 where you get an option of having a shortcut
to the secure database.

That's not really an option. You want to remain joined by default to
system.mdw. Access will use that for all sessions. When you create
a desktop shortcut, it will use the /wrkgrp switch which will
over-ride the default and use the specified mdw file *for that
session*. Opening Access any other way will use the system.mdw and
no login will be required.

3. Also after I went thru all 32 steps, why do I need to go thru
the steps below to join the default System.mdw file? Then if I do
that, I would not able to the database at all. Why would I want to
do that?

See above.

4. Now my FE database (and other 3 linked to the FE) are protected.
When I click on the FE (and the other 3), the database will open and
prompt me for a user name and password. Is it secure now?

A good test is to rejoin system.mdw and then try to open these
databases by double-clicking on the file in Windows Explorer. You
should not be able to even open them.

5. I assigned one of the users to Full Data Access, Read, and
Update. After I tried to get into the database with that user, why
did I able to get into the design and change and create the design
an object?

You can open the mdb and go to Tools, Security, User and Group
permissions and verify the permissions that this group has. I don't
believe the Full Data Access group prevents the creation of new
objects. You may want to uncheck their 'modify design' permissions
though. Remember that when you are looking at permissions, you want
to look at 'group' permissions, not user permissions.

--
Joan Wild
Microsoft Access MVP



.

Relevant Pages

  • Re: security wizard cannot be run
    ... You need to open your database using your secured mdw (i.e. the desktop ... Open Access (not via the shortcut). ... Create a new mdb and import everything from your 'secure' mdb. ... Once the database opens, the ...
    (microsoft.public.access.security)
  • RE: security wizard cannot be run
    ... secure mdb while joined to system.mdw. ... database is very secure) ... Open Access (no mdb). ... Once the database opens, the ...
    (microsoft.public.access.security)
  • Re: Join a Workgroup
    ... shortcut in order to open your secure database. ... the Users Group, you can't change that. ... I now am try to split my database by using the instructions you provided ...
    (microsoft.public.access.security)
  • RE: Check for Exclusive
    ... A shortcut needs to be on each user's desktop. ... NEVER use drive map paths in a multi user environment. ... First split the database so that all the data is in one mdb and the ... If a user opens the database when it was not previously open, ...
    (microsoft.public.access.modulesdaovba)
  • Re: With and Without (not Pink Floyd)
    ... > I have an Access 2000 database running on WinXP that uses two shortcuts to ... One shortcut is for the administrator that uses the MDW ... > "regular" users that opens the MDB file without security. ... First off, all Access databases use an mdw file, by default this is ...
    (microsoft.public.access.security)