Re: security only works on my PC

Since it isn't secured properly yet, don't distibute it. About splitting:
http://www.granite.ab.ca/access/splitapp/index.htm
http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

You really do want to split it. First get the security working properly on
the single mdb.

Open it using your shortcut and log in. Go to Tools, Security, Permissions.
Click on the Groups option and select the Users Group. Now go through every
object and ensure that the Users Group has no permissions (don't forget the
Database Object). Next click on the Owner tab, and go through every object
and ensure that Admin is not the owner of anything.

Now test again via Windows Explorer - you shouldn't be able to open the mdb.

Once you have the security working, then split it. However don't use the
splitter wizard, as that will result in an unsecure backend. It is simple
to split it manually. Follow the steps at www.jmwild.com/SplitSecure.htm

--
Joan Wild
Microsoft Access MVP

brem219 wrote:
Well, then I guess I did something wrong because I was able to open
it with ease through Explorer. I didn't even need a name or password.

Also, I've read a lot on this board about frontends and backends and
I'm not sure how a database would be split or why it should be done
at all. My database is all at one location, in a folder on the
network.

"Joan Wild" wrote:

brem219 wrote:
OK, thank you. I rejoined the system.mdw workgroup and set up the
shortcut successfully on my PC. I had already removed permissions
from the users group and replaced them with RWOP queries so no
problem there.

Now I want to do the same thing on my co-workers' PCs. Do I have to
go to each of their PCs and link to system.mdw and create the
shortcut just like you showed me?

Before you go to each user's PC test that your database is secured
properly. Just open Windows Explorer and double click the 'secure'
mdb. You shouldn't be able to even open it. If you can, then it
isn't secured properly.

Once you have it tested, yes you need to provide the shortcut and the
frontend to each user. If you are confident that everyone has a
typical installation of Access, you can just copy the mdb and copy
the shortcut (it's a file with a lnk extension).


"Joan Wild" wrote:

brem219 wrote:

You need to use the
workgroup administrator to rejoin the system.mdw workgroup file
that ships with Access.

I don't know what this means. I opened the workgroup
administrator but only saw the new workgroup I created when I
added security. If there's another one, where do I find it?

It depends on version, but it usually is in the windows system
folder. Use Start, Search, and look for *.mdw on your hard drive.
Be sure you include system and hidden folders in the search, and
make a note of the path(s) it finds. You are looking for
system.mdw. When you open the Workgroup Administrator, click on
Join and rejoin the system.mdw. You should now get no login when
opening a mdb.

Then use a desktop shortcut to launch your secure mdb The
target would be
"path to msaccess.exe" "path to mdb" /wrkgrp "path to secure mdw"

I don't know how to do a shortcut. Do I just right click on my
desktop and type in exactly what you wrote?

Right-click the desktop and choose New...shortcut. Click on browse
and locate msaccess.exe (it'll be something like c:\Program
Files\Microsoft Office\Office11\) and finish. Go to the desktop
and right-click this shortcut and choose properties. It'll open
to the shortcut tab, and you'll see the target line with the path
to msaccess.exe. Just edit that and add the path to mdb, the
switch, and path to secure mdw.

I want my the 6 users to be able to open the database. The
database is configured so that users will be able to access the
tables through a series of queries, but not look at or change the
tables. I'm not sure about changing the permissions. I've
adjusted the permissions on my PC so that 2 of the 6 users have
admin priveleges, and the ability to look at tables and change the
database.

Normally, you would not assign any permissions to the Users Group
when securing a database. The exception would be if you want
security, but don't want users to have to login. If you assign
permissions to the Users Group, then they don't need your secure
mdw. They can use the standard system.mdw on their system, and not
log in.

It is possible to remove all permissions on the tables, and then
use run with owner permission (RWOP) queries for all data
interaction. However, usually you'd provide a form for users to
use, rather than just a query.

--
Joan Wild
Microsoft Access MVP


.

Relevant Pages

  • Re: need help... ftp with asp
    ... a good idea to suggest someone modify their security settings. ... and in a good secure setup, ... permissions on the file, not all the methods that can be used to delete ... you're at risk. ...
    (microsoft.public.inetserver.asp.db)
  • Re: Cant open db from Excel due to Access security
    ... secure a db but allow users to access certain areas using their own ... wrong when securing it but on checking the security settings all looks ok. ... > You cannot open a mde/mdb in Excel, but you can use Get external data. ... In the Developer.mdw the Users group has Read Design & Read Data ...
    (microsoft.public.access.security)
  • Re: Default NTFS permissions too liberal on newly created volumes
    ... it sounds like your users had excessive share permissions. ... read share permissions they would not have been able to create folders. ... Windows 2003 Server Security Guide and the Threats and Countermeasures Guide ... > brings liberal permissions to the root of the drive for the USERS group. ...
    (microsoft.public.windows.server.security)
  • Re: Securing Back-End, Using one .mdw file on FE & BE
    ... It sounds as though the Users Group still has Open permission on the Database Object - double check that. ... You open a session of Access using your secure mdw and logging in as the user you want to be owner. ... Remove permissions for every object for the Users Group ... I am using a shortcut to open the FE, I have gone through all appropriate steps to properly secure the DB. ...
    (microsoft.public.access.security)
  • Re: Unsecuring a secure Access Database?
    ... you need to grant all permissions to the Users ... You should also ensure that Users group has all permissions to ... I would double-check that I had copied the secure ... The database has served me well as a 'stand alone', 'single-user' tool, ...
    (microsoft.public.access.security)
Loading