User-proofing an Access Application
Posted on 2011-03-11
I'm creating a new routine for all my apps that will "clean" everything up before I release the tool.
I'm looking for best practices and advice for what I should include in the lock-down of my tool. Here are some of the things I'm looking to do:
1. Make my administrative forms and reports inaccessible or password protecting them somehow so I can access the stuff I need to but users can not.
2. Setting the current database properties to hide the application objects (tables, code, etc.)
3. My user base isn't too very technically savvy, so some of the "tricks" (like holding down shift when opening the app) aren't going to be a problem.
4. I don't have any security issues with the data, but I want to keep users from hurting themselves :) or accidentally breaking something.
I am not a fluent coder (yet) and any code snippets would be greatly appreciated.