I have built a basic database using Microsoft Access 2010 as a tool meant to improve the logging of information (prior, the information was manually collected into very messy Excel spreadsheets). Now, there is a simple form that auto-populates the relational tables cleanly and in a standardized manner.
Long story short - if I want to hand this database back to the team who were originally logging the information, are there simple yet effective gold standards for "user-proofing" the database beyond hiding critical sub forms, disabling non-form views, and removing toolbars from view? I have also read up on splitting the database, which could be a path forward as well to secure the back end of the database. The team isn't very fluent with Excel beyond basic functions, and I expect to train them up on Access usage at least to a basic capacity so they can maintain the database themselves long-term.
The specific goal is to protect the input enough so they are not likely to edit the actual tables and break the relationships
