I am just about complete with setting up my first database and I am trying to figure out the best way to set up my security on it. I was thinking about setting it up using a MDE file, but my only concern is once I set it up as a MDE file, will I be able to go back in and make changes? I know because it is a new database, I will need to add more forms and reports. And if I can not do this, what would be the purpose of ever setting it up as an MDE?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
MDE File
- Thread starter 3063
- Start date
Hi,
Back up your 'development copy' elsewhere, then create your MDE.
You can't change the MDE, but you can update your development copy and create an updated MDE.
regards,
Darrylle
Never argue with an idiot, he'll bring you down to his level - then beat you with experience. darrylles@hotmail.com
Back up your 'development copy' elsewhere, then create your MDE.
You can't change the MDE, but you can update your development copy and create an updated MDE.
regards,
Darrylle
Never argue with an idiot, he'll bring you down to his level - then beat you with experience. darrylles@hotmail.com
Usually, production systems are split into a front end (forms, reports, modules, queries, macros) and a back end (tables). You would create an MDE for the front end to prevent modification of that portion but leave the back end as an mdb (usually password protected). Of course, when you create the MDE, you keep an mdb copy so that you can change it and generate a new MDE as needed.
As to security, the rule-of-thumb is that you should have sufficient security to make it more costly in time and/or resources to crack the security than it is to get the information by legitimate means. Full 512-bit encryption on your To-Do list is a waste of effort.
Usually the security features provided by Access (passwords, restrictions on rights, encryption) are sufficient for most purposes.
As to security, the rule-of-thumb is that you should have sufficient security to make it more costly in time and/or resources to crack the security than it is to get the information by legitimate means. Full 512-bit encryption on your To-Do list is a waste of effort.
Usually the security features provided by Access (passwords, restrictions on rights, encryption) are sufficient for most purposes.
- Status