Re: Hlp - DB security mystery

Hi Joan,

I will look at the manual steps and follow them.

In answer to your question, I have indeed had previous versions of Access on
this computer. One of the other computers has as well, but the others are
brand new.

I have found that joining the MyWrkgroup.mdw, logging on as MyAdmin and then
creating a brand new db and importing all objects, then setting the
permissions works. I'm just not sure why.

The in point steps I followed based on your instructions (I hopefully have
done so!):
1. Create NewDatabase with system.mdw and save
2. Close Access
3. Open Access but *not* NewDatabase
4. Create a new workgroup file, MyWorkgroup.mdw, and join it
5. Tools, Security, User and Group Accounts
6. Add new MyAdmin user
7. Add MyAdmin to the Admins group
8. Remove the Admins group from the Admin user
9. Add a password for the Admin user

10. Close Access
11. Reopen Access
12. Open the NewDatabase
13. When prompted for user name, make sure it’s the MyAdmin user – there is
no password set yet
14. Tools, Security, User and Group Accounts – add a password for MyAdmin

15. Close and reopen Access and NewDatabase, logging on as MyAdmin with
password
16. Tools, Security, User Level Security Wizard
17. Modify the current workgroup, Next
18. Leave all objects selected to make sure all will be secured, Next
19. Leave default groups unchecked – we will not use them, Next
20. Make sure Users group has no permissions on anything, Next
21. Add new users to avoid having to log in individually later to set their
passwords then Next
22. Click Next again, as we will create groups and assign permissions later
23. Click Browse to choose a location for the unsecured bak file of your db
24. Finish
25. Print and save snapshot report
26. Access closes, encodes and reopens the db, plus places a shortcut to it
using the MyWorkgroup.mdw

27. Close the database
28. Rejoin the system.mdw workgroup

29. Test the desktop shortcut to open the db with your user name and password
30. Set permissions by adding groups and assigning users to the groups

31. Open Windows Explorer and make sure that you can’t double-click the db
to open it.

Am I missing something?

Thanks so much!

--
Thanks!

Dee


"Joan Wild" wrote:

What version of Access on your computer? On their computer? Has there ever been any other versions of Access on either computer?

As Keith says, you can secure it manually; read the security FAQ and you can follow the manual steps outlined on the 97/2000 page at my website. If you've studied the FAQ/whitepaper/etc, then the steps should make sense to you.

--
Joan Wild
Microsoft Access MVP
"dee" <dee@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:04509EC9-58E1-456A-B496-825EBFF13641@xxxxxxxxxxxxxxxx
Hi,

I have successfully secured a number of databases - practised on many in
order to gain a good understanding of security and then enforced security on
my database.

I followed Joan Wild's instructions and successfully secured the db - when I
finished, I set the system.mdw back, went to Windows Explorer and tried to
open the db and got the message saying I didn't have access. Used the
shortcut on the desktop and was prompted for user name and password. All was
working very well.

The db will have data entered by a few users, so went to one of their
computers, logged on as a data entry user, and tested opening from Windows
Explorer - no problem. I triple checked the mdw and the Users group has NO
access, the Admin user only has access to the Users group and my users are
part of a DatabaseEntry group which has non-admin rights (I am the only user
with Admin permissions) but access to forms, queries, etc. in order to input
data.

I then logged on as administrator, unsecured the db by granting User group
all permission, making sure to join the system.mdw and then creating a new db
and importing my tables, forms, queries... Then followed all of the steps
to secure, including creating a brand new mdw. At the end of running the
user level security wizard, it says the db is secure, the snapshot indicates
it is secure, everything looks fine. But, again - I can just double-click
the file and open it in Windows Explorer.

The database in on a network share to which only my group and I have access.

Is it possible that it's something that the network people did when setting
up the share?

If anyone has encountered this problem, I would really appreciate any advice
or ideas. I am totally stumped.

Thanks!
--
Thanks!

Dee

.

Relevant Pages

  • Re: Hlp - DB security mystery
    ... Joan Wild ... I triple checked the mdw and the Users group has NO ... to secure, including creating a brand new mdw. ... The database in on a network share to which only my group and I have access. ...
    (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: Why is this so hard?
    ... workgroup information file that the database is secured with. ... understand how to put the secure shortcut on the users' computers. ...
    (microsoft.public.access.security)
  • Re: Secure Database Systems
    ... > I was wondering if it is possible to create a secure database system ... > scripting/programming language(Perl, PHP, Ruby, Java, ASP, etc) combination? ... > imagined in the database. ... > computers. ...
    (comp.lang.php)
  • 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)