- Shopping Bag ( 0 items )
Author Garry Robinson approaches this book differently than other Access books on the market: he keeps the focus on issues that will help protect your database. Written from an experienced developers point of view, he discusses protection and security task-by-task. This book is even recommended among Microsoft TechNet Security Topics: Threats and Countermeasures.
Youll learn to hide tables as system tables, produce databases that are difficult to crack, and back up databases. You will learn how to keep staff from viewing salary tables, prevent customers from peeking at your distributed software design, and become a better judge of worthwhile security options (versus time-consuming choices).
|About the Author|
|About the Technical Reviewer|
|Ch. 1||The Access Protection and Security Driving Instructions||1|
|Ch. 2||Protecting Your Database with Startup Options||23|
|Ch. 3||Using Database Options and Attributes to Protect Data and Objects||49|
|Ch. 4||Providing a Solid Foundation with Good Programming Practices||81|
|Ch. 5||Backing Up and Recovering Your Databases||109|
|Ch. 6||User and Object Surveillance||161|
|Ch. 7||Protecting Your Database with Menus and Toolbars||197|
|Ch. 8||Developer Workgroup Security||233|
|Ch. 9||Security Concerns, Encryption, and Database Passwords||287|
|Ch. 10||Securing Data with Workgroup Security||307|
|Ch. 11||Object Protection and Security Measures||363|
|Ch. 12||Protecting and Securing Your Database with the Operating System||403|
|App. A||Specific Access Security Information||453|
|App. B||Registering the Access Workbench||459|
|App. C||Why Migrate from Access to SQL Server?||461|
Posted October 26, 2004
As advertised, I found the book very readable. Garry transforms a rather dry and gritty subject into an almost chatty style that is easy to manage. It only took me a couple of days to read all 500 pages and even though I am an experienced developer, I picked up a lot of useful tips. Garry writes specific information for different readers - the developer, the end user, the database administrator. Each has different requirements. For some applications, workgroup security is essential, for other it is not. Garry goes into Workgroup security in considerable depth, but in a logical and understandable way. He explains that there is more than one way to secure a database. It all depends who the users are, who the market is, and the liklihood of people trying to do the wrong thing. Protecting users from themselves is a noteable part of the process. Garry looked at a lot of things that you might not consider as security issues, but which can make a big difference - menus, startup options, backups, user surveillance, error handling, coding practices. Securing your database against loss and corruption is at least as important as foiling hackers. With workgroup security, I particularly liked the idea of securing just one object. This stamps your ownership on the app, and keeps the client from going too far without your input. This book will suit all those using or developing access applications. Especially those who want to keep away from 'complex' workgroup security, you too will find a lot of very useful information here. This will allow you to keep a few steps ahead of your clients.Was this review helpful? Yes NoThank you for your feedback. Report this reviewThank you, this review has been flagged.