Confusion with Front/Back end split database

JamesN

Registered User.
Local time
Today, 21:24
Joined
Jul 8, 2016
Messages
78
Hi,

I'm currently running an access database on sharepoint 2013, both front and back end are stored on sharepoint (access 2010) The front end consists of a form which is linked to a data warehouse table stored in the back end.

My question is, how can i stop users updating the data warehouse table which is stored in the front end of the file? my concern is that users can open the table in the front end and make changes/delete records. All i want them to be able to do is add new records via the form and not see the data warehouse table if possible.

I've tried hiding the table in the front end but it re-appears when publishing to sharepoint.

Any help is appreciated
 
  1. HIDE the Navigation Pane
  2. open the form when the database opens
  3. MAXIMIZE the form size
  4. instruct users to use the form only

NOTE: SharePoint lets you limit the network users that have access to the site that you are posting the database on, if you choose to go that way.

This will provide optics that will hide the database objects from the compliant user. If you cannot trust your users to follow the DBA authorized Training, then they should not be allowed to use the database. You can create a login protocol to validate assigned UserIDs and even individual Passwords if necessary to keep out unscrupulous and uninvited "Users". It will also mitigate curious users from seeking to modify objects or append data in ways that were not intended by the DBA. (See other posts with keywords like Database User Security)

Lockingdown a database with tight security always raises the question of WHO really needs access to this data and this database. Also if there is a trust issue then something along the lines of a Non-Disclosure Agreement backed by enforceable consequences for tampering with or using the database in a way it was not designed to be used will have to be put in place, signed, and kept as a record for each user. In addition the database itself may need to keep an Audit Trail of changes made to the data which would include the time the change was made and by Whom. This will promote accountability.

Even MS Access database administration can be a very serious undertaking, as with any database.

If you have more detail questions, just let us know.

CHeers!
Goh
 

Users who are viewing this thread

Back
Top Bottom