Now an mde/accde surprisingly does not lock down tables, queries or macros.Īlso note that since all VBA code is locked down and unviewable, any unhandled errors will cause a fatal application crash, hence the crucial importance of bulletproof error handling throughout all of your VBA code. So in essence by distributing a compile version you minimize any opportunity to mess around with the database itself. Users can not open Forms or Reports in design view, nor can the view any of the VBA code. By converting your mdb/accdb into an mde/accde, you lock down certain type of objects within your database. Distribute a Compiled FE to your End-UsersĪnother critical step is to always distribute a compiled version (mde/accde) of your FE to your end-users. This will, in the very least, stop prying eyes from being able to harvest BE passwords allowing anyone to have complete reign on your raw data.Īlso, be sure to use a different password for the FE than used with the BE. As such, like your back-end (BE), you should always Encrypt with Password your front-end (FE). Password Protect your FEĪs I pointed out in my post entitled Why Ms Access Isn’t A Secure Database – Part 2, a MS Access Front-End is not secure and leaves sensitive information completely open to hacking. In this post I’d like to discuss what steps you can take to try and secure, as best you can, your MS Access Front-End application.

Ms access password protect vba code