Protected database without log-in

  • Thread starter Thread starter amber
  • Start date Start date
A

amber

My users don't want to have to log into the database, and
I do not want them to be able to alter my tables and
relationships.

I have read the security FAQ a half dozen times,so I have
a feel for the security model. I believe #8 in the FAQ
addresses my issue--Protecting just code without users
having to log in.

Do I distribute the shortcut for the front end linked to
the unsecure file for my users--because it uses the
default SYSTEM.mdb file? Or am I missing an important step
in the process?

Thanks, in advance!
 
Hi Amber,

Step # 8 just states you distribute 2 files:
1- your secured MDB
2- MDW file with Admin account no password (or another MDW
file)

The key issue whether you have a split database or not is to DO NOT
distribute the correct MDW file or distribute the correct MDW but make sure
the Admin account does not have a password. This way everybody logs in as
Admin.

Think of it as if you secured your database using MySecured.MDW and the
users open your database using the following shortcut:

C:\<full path to msaccess.exe> <full path to your database> /wrkgrp <full
path to MDW where the Admin account does not have a password>


I hope this helps! If you have additional questions on this topic, please
respond back to this posting.


Regards,

Eric Butts
Microsoft Access Support

"Microsoft Security Announcement: Have you installed the patch for
Microsoft Security Bulletin MS03-026? If not Microsoft strongly advises
you to review the information at the following link regarding Microsoft
Security Bulletin MS03-026
<http://www.microsoft.com/security/security_bulletins/ms03-026.asp> and/or
to visit Windows Update at <http://windowsupdate.microsoft.com/> to install
the patch. Running the SCAN program from the Windows Update site will help
to insure you are current with all security patches, not just MS03-026."



--------------------
| Content-Class: urn:content-classes:message
| From: "amber" <[email protected]>
| Sender: "amber" <[email protected]>
| Subject: Protected database without log-in
| Date: Mon, 9 Feb 2004 11:58:20 -0800
| Lines: 15
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcPvRxEEbzHj8/4gRZKOxWoG0noxPQ==
| Newsgroups: microsoft.public.access.security
| Path: cpmsftngxa07.phx.gbl
| Xref: cpmsftngxa07.phx.gbl microsoft.public.access.security:8192
| NNTP-Posting-Host: tk2msftngxa11.phx.gbl 10.40.1.163
| X-Tomcat-NG: microsoft.public.access.security
|
| My users don't want to have to log into the database, and
| I do not want them to be able to alter my tables and
| relationships.
|
| I have read the security FAQ a half dozen times,so I have
| a feel for the security model. I believe #8 in the FAQ
| addresses my issue--Protecting just code without users
| having to log in.
|
| Do I distribute the shortcut for the front end linked to
| the unsecure file for my users--because it uses the
| default SYSTEM.mdb file? Or am I missing an important step
| in the process?
|
| Thanks, in advance!
|
 
Thanks for explaining this so clearly for me. I was
really getting caught up in the fact that the database was
split.

Thanks!
 
Back
Top