Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Security / July 2006

Tip: Looking for answers? Try searching our database.

Preventing design changes with share-based security

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
rumbledor@hotmail.com - 27 Jul 2006 21:38 GMT
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 - 28 Jul 2006 01:46 GMT
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

>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.
[quoted text clipped - 7 lines]
>
>What would be the best method for implementing this?

--
jackmacMACdonald@telusTELUS.net
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.