----------------------------------------
            Microsoft Access Version 1.1
           Security Wizard 1.1 README File
                   September 1993
	  ----------------------------------------

	  (C) Copyright Microsoft Corporation, 1993


------------------------
How to Use This Document
------------------------

To view README on screen in Windows Notepad, maximize
the Notepad window.

To print README, open it in Windows Write, Microsoft
Word, or another word processor. Then select the entire
document and format the text in 10-point Courier before
printing.


--------------------------------
Microsoft Access Security Wizard
--------------------------------
To install the Security Wizard, copy wzsecure.mda into your Microsoft
Access 1.1 program directory.  Add the following line to the
[Libraries] section of your msaccess.ini file:

    wzsecure=ro

If it doesn't already exist, add a [Menu Add-Ins] section in your
msaccess.ini file, and add the following line to it:

    Security &Wizard==swz_SecureDB()

The next time you start Microsoft Access, the Security Wizard command
will appear on the Help menu.  To start the Wizard, select this
command.

----------------------------------------------
What the Microsoft Access Security Wizard Does
----------------------------------------------
The Security Wizard will only run on Microsoft Access 1.1, but will
work with databases in 1.0 or 1.1 format.  Attempting to use the
Security Wizard with Microsoft Access 1.0 will result in "Out-of-data
database format", followed by "Some library modules could not be
loaded" when you start Microsoft Access.

The Security Wizard can take quite a while to run.  For instance,
securing nwind.mdb on a 486/50 takes approximately 13 minutes.

The steps the Wizard takes to secure a database are:
1. Creates a new, encrypted database with a
   name you specify.
2. Prompts you for the object types you want to 
   secure.  Objects are secured by revoking the 
   permissions of the Users and Guests groups
   on them.
3. Exports all the objects to the new database.  This
   includes recreating attached tables and table 
   relationships.
4. Secures the object types selected in step #2.
5. Updates several internal data structures in the
    database to ensure security.

The original database is not changed in any way!  All objects in the
current database are exported to the new one.  This includes
recreating table relationships and attachments to tables in other
databases.  If you have attached tables, the native table (in Access,
Paradox, SQL Server, etc. format) must be accessible.

The new database is completely secured.  The new database will be in
1.1 format, regardless of the format of the current database.  If you
must have your database in 1.0 format, you can use compact to convert
it back.

The current user is the owner of the new database and all objects in
it.  The Admins group of the current SystemDB has Full Permissions on
the database and all objects in it.

Object types selected in step #2 are completely secured from other
users by revoking permissions from the Users and Guests groups. 
Objects types not selected in step #2 are copied to the new database,
but the Users and Guests groups still have permissions on them,
leaving them unsecure.

NOTE:  Permissions on objects in the current database are not copied
to the new database.

If you create new objects in the secured db at a later time, they will
be unsecured, because the Users group has Full Permissions on all new
objects.  This is the default for Microsoft Access.  If you wish to
secure these objects, use the Permissions dialog to revoke permissions
from the Users and Guests groups.