Total Access Startup guarantees that your users always launch the right version of Microsoft Access with the right version of your Access database.
Can Total Access Startup prevent users from getting around this tool by simply opening their local copy of the front-end file that’s deployed to their desktop?
No. After Total Access Startup installs the front end database to your user's PC, there's a possibility your user could open Access and the database and run it without launching it from Total Access Startup.
Total Access Startup cannot limit what users do in Access. There are lots of things users can do in Access or your front-end database if it's not properly designed and secured. These issues would exist whether Total Access Startup is used or not.
There are several ways to limit these issues with Microsoft Access databases
- Deploy your database as an ACCDE or MDE so that users cannot modify/see your forms, reports and module code.
- Make sure your database has startup routines that launch when the database opens. This lets you control what your users can and cannot do.
- Advanced Tip: Set the database's AllowByPassKey property to False to prevent users from skipping the startup by holding down the shift key. This needs to be done carefully so you don't lock yourself out.
- Total Access Startup supports the use of a table with the version number in the front-end database to compare against a copy that's already deployed. You can also keep a similar table in the back-end database for your application to check against. If the front-end database sees that it's out of date, it can refuse to run. This prevents an old front-end database from running. Your user would then need to run the link for Total Access Startup to refresh their copy.
Please sign in to leave a comment.