Editing a secure MS Access Database in 97 SR2

[timrob]

I have a database that multiple users input data too, which I'll call version 1. It was created in MS Access 97 SR-2. It has an interace, tables, and some code. On a backup copy, I secured the database, which also made it much smaller 23.7mb to 3.8mb. So far, in the secure DB, I'm able to add new users, delete users, update tables, edit existing code, and make changes to the current interface.

In version 2.0, I'm going to add several new features, some buttons with code behind them, and a few more tables.

My questions are:
1. Can I reverse the "DB securing" process?.
2. Is there any point to question #1. Is there any reason I can't simply add the new features to the secure/compressed version 2.
3. Other than a smaller file, what does securing the DB give me? Does it speed up the use of it? Does it actually give me a bit more security? This is not a high security DB that if somebody hacks it that the world will end.

 

[IanAble]

If by securing the db, you mean you created an mde file. No you can't make any changes to it. Creating an mde file secures you code since class or general module code can't be viewed.

If version 2.0 is just an mdb file then open it up as the owner (the user which created the file) or member of Admins (if you given the Admins group administer database permissions) and you should be able edit any of the database objects.

In general securing the database by using jet security and creating an mdb file is useful since you've done all you can to protect the data (a legal requirement if any personal information is stored) and the database from curious/malicious users or others...

 

[timrob]

IanAble,
Thanks for the info. The new secure file is a .mdb.

Will I be able to reverse the securing process?

 

[IanAble]

If you open the mdb file with a user with database administer permissions you can assign administer database permissions to the Users group, and then give the Users group full permissions for all other database objects.

This means that any user in any mdw file can open the file with full permissions. This should only be used so that you can import all database objects into a new database file (opened with default system.mdw or other custom mdw as the workgroup information file) and sort out your own permissions.

I cannot say this often enough. If you don't secure the database your users will be able to do anything they like, whether they mean to or not.