There aren't too many threads on this subject folks. I am looking to understand this a bit more. From what I know, complete security of a database can only be accomplished by making an MDE file. But, the downside there is that MDE's cannot be edited by anyone, so any backups or changes that need to made must be done with an MDB.

So, what I want to know is, if I want complete security of a database (as in, no changes allowed to be made, except by me), my only option is to make an MDE file and then transfer all the data back and forth between that and an MDB file whenever I need to make any design changes.

Am I right?

Thanks!

What you call a downside I call an upside; the users can't change anything. The average user wouldn't know what to change anyway, so it protects them from accidentally changing anything. I only distribute MDE's to users.

You don't have to transfer data back and forth, you split the app and just replace the front end when you make changes.

I'll check on that Paul, thanks.

And the upside/downside thing to this isn't the point. I just said that because this is about processes for my own personal use. There will no be no outside users involved.