Preventing design changes with share-based security

[rumbledor]

I have an Access 2003 (might be 2000 format, actually) in which I would
like to prevent users from making any changes to any database objects.
This database uses share-based security to minimize security
maintenance. Everyone with access to that network share may
read/write/delete data as they desire.

The requirement is that no passwords be implemented unless a user
attempts to modify an object in the database, and no user-level
security be implemented in the database itself.

What would be the best method for implementing this?

 

[jacksonmacd]

Split your database into a frontend component (forms, queries,
reports, etc) and a backend component (tables only). The backend
belongs on a shared folder on your network server, while each
workstation should have its own copy of the frontend.

http://www.granite.ab.ca/access/splitapp/index.htm

Once you have split the database, you will want a method to
automatically distribute any modifications to the various
workstations. Many people use:

http://www.granite.ab.ca/access/autofe.htm

Distribute the FE as an MDE file instead of MDB file. No changes are
allowed in MDEs.

Implement Access UserLevelSecurity on the BE, and allow ReadData
permissions to all the tables to the Users group, but deny them the
permission to modify the table structure. By allowing Users to enter
data, then anybody using an unsecured workgroup file will be able to
login as the Admin user and have permission to modify the data.

Access user security is not to be taken lightly, so read very
carefully and thoroughly, practice on a COPY of your database, and
don't skip any steps in the process.

Here are a number of links about security:

http://home.bendbroadband.com/conradsystems/accessjunkie/resources.html#Security