You can publish your own PDF file online for free in a few minutes! Sign Up. Recommend Papers. Real World Cryptography [Early Access ed. Real The authors handle c 54 3MB Read more. Programming Microsoft Office Access Use this guide to get professional-level instruction to build more powerful multiuser database applications using Micros 22 17MB Read more. This service is more advanced with JavaScript available.
Authors Garry Robinson. Shows how to secure a database to reduce the risk of code cracking software Gives testing software for reviewing security settings Gives easy-to-use samples that can be imported into a database. Front Matter Pages i-xvii. Pages Protecting Your Database with Startup Options. Backing Up and Recovering Your Databases. User and Object Surveillance. Protecting Your Database with Menus and Toolbars. Developer Workgroup Security.
The download that comes with the book includes an Access database with code to handle the above-described settings more gracefully than what I have published here.
If, for example, the property does not exist and you attempt to read or write to it, you get an error. If, on the other hand, you try to create it and it does exist, that also generates an error. Garry's code takes care of all this, encapsulated into a form that may be imported into any Access database and used with your applications. Another trick that falls more in the protection category than security is the ability to hide database objects, such as tables.
This is the tip alluded to above that is my favorite. Keep in mind that it only works for versions and greater, but it is a nice line of defense. Access 97 did expose an attribute for tables called dbHiddenObject, but as Garry points out, setting this attribute to true would flag your table as temporary and it would be deleted during the next compact. Newer versions of Access actually expose an application method for hiding and showing objects programmatically.
Of course, if users can get to the Options form from the menu, they can simply toggle the Show Hidden Objects option to true and see your hidden forms, queries, etc.
Here are some examples of reading and writing hidden attributes. This chapter mentions two other really cool features that work with all versions of Access, but apply only to tables. One way to hide a table is to name it with the prefix of Usys. Therefore, if you create a new table and name it UsysCustomers, it will disappear from the database window.
The other cool trick is to set the attributes of a table to dbSystemObject. Doing so causes the table to be treated like the Msys system tables. Not only does this hide the object when the Show System Objects option is cleared, it causes the tables to be non-updateable from the database window. You cannot add or edit records in any table that has this code applied to it:. The strange but useful oddity to this setting is that, while it is not editable from the database window, it still works fine when bound to a form.
This is a simple and effective way to protect data in tables from power users who may like to browse data casually. The next few chapters discuss topics that one may or may not ordinarily associate with security. For example, Garry looks at each of the following from a security and protection standpoint. From what I gleaned, I am going to split the security topic into two segments: Access Workgroup Security practices and Windows Operating System security issues. As mentioned above, the suggestions given for using Access security are not topics I have seen covered in many of the other Access programming books I have read.
0コメント