Sending a Database on After Security has Been Implemented

[NonAccessGuru]

About 3 years ago I created a membership tracking database for a club I belong to. It was handed off by me and used by two different membership directors. After this length of time the club decided there were other options that needed to be added to the database so I have re-designed it. In getting the database back for revision I found it to be a mess after 3 different people had gone into the objects making changes and basically making it worse than what it was. At the time I created it I did not implement any security into it.

So security was in order for prying eyes and hands (something I had never done)....after creating a new workgroup and admin and user accounts I've applied permissions to the user level account limiting their access to objects so they can't be changed. All they basically see is the switchboard and a membership information input form. I also went into "Startup" and unchecked all the boxes. I followed and implemented the "disable shift key" posted by MadMaxx (thanks, Max!) as a module with two macros that enable/disable it. The enable option is hidden on the switchboard (which, by the way, works great!).

Note that the database is not used on a network but on one individual's personal PC in their home. It appears to me that because I have made a new workgroup and applied permissions for the admin and user that I cannot create a MDE file (which is grayed out).

Is creating a MDE file a security alternative to creating a workgroup with respective admin and user permissions to keep unauthorized eyes and hands out of the objects? (the membership director's husband feels he is God's gift to Access designers...I've seen his work...he isn't)

When I hand off the database to the club will the database (as it sits as a MDB file) retain all the security implemented if the system.mdw file ISN'T included or is the security I've implemented internally embedded in the (one file) database?

Thanks in advance for any input!

Rod

 

[MicroE]

The MDE file will lock down the objects to prevent users from accessing the design view (forms, reports, modules). I use this in place of workgroup security if locking down my application is the goal.

The mdw files needs to be distributed along with the mdb/mde. Not having it could prevent users from accessing the objects (depending on how permissions were applies).
http://www.databasedev.co.uk/microsoft-access-mde.html

 

[NonAccessGuru]

Thanks, MicroE, for the reply. If I understand you correctly if I include the "system2.mdw" file (I created as a new workgroup) containing the secuirty I've implemented along with the database (both in the same folder...) then the security requiring a username/password and permissions should remain in tact.

(If I'm incorrect here please correct me...)

Thanks again!

Rod

 

[MicroE]

The security is intact regardless of the workgroup file. However, the username and permissions would be missing, which could prevent users from accessing the application.

If I gave you a mdb file with User Level Security set up, but not the mdw file – you would be limited in what you could do. You may not even be able to use the application at all. If I ever lost the mdw file, I could potentially be locked out of the database forever.

I would rename the system2.mdw to the YourApplicationsName.mdw – so it is not confusing. When you deliver the product, you will need to add the /wrkgrp switch in the shortcut in order to implement the security.

http://office.microsoft.com/en-us/access/HP051883001033.aspx?pid=CH010043151033

http://support.microsoft.com/kb/305541/EN-US/