I have a backend on our server and a front end running on individual workstations. I have applied the shift enter lock (referred to in these forums and downloaded from Utteraccess.com) on the front ends and made them reasonably bullet proof by customizing menus, turning all forms into modal pop-ups, hiding the database window, and controlling navigation through command button forms. My problem is that I want to lock all end users out of the back end tables while still allowing them to enter/edit data in those tables. I was hoping to accomplish this using Windows network security, but this prevented the end users from moving data to and from the back end via the linked tables. I have searched these forums for posts on "security," "back end," "front end," etc., and am coming to the conclusion that I need to abandon network security in favor of access security. All of my tables and reports in the front end are run through queries, so I was hoping to be able to follow the advice of the following post http://www.access-programmers.co.uk...s=&threadid=40109&highlight=backend+security.
The problem here is that I have already developed the front and back end and am unsure how to go back and follow the instructions given in the post.
I have tried to use the security wiz and have ended up with a database that I can no longer open at all. Fortunately, I am experimenting with security on a copy of the original db. Any ideas on how to proceed?
The problem here is that I have already developed the front and back end and am unsure how to go back and follow the instructions given in the post.
I have tried to use the security wiz and have ended up with a database that I can no longer open at all. Fortunately, I am experimenting with security on a copy of the original db. Any ideas on how to proceed?