Microsoft Access 2010 Bible

(Rick Simeone) #1

898


Part IV: Professional Database Development


Tip
In this chapter, the expressions end user, user, client, and customer all mean the same thing: the person or
group of people using the application you’ve created. Although the terms client and customer are normally
applied to the parties who pay to have the application produced, thinking of all users as clients should be your
first step toward producing bulletproof applications. Always think of your users as the important people they
are, and your work will reflect a conscientious attitude and a professional approach.


Introducing Bulletproofing


Advanced database systems like Access bring valuable data and information directly to the user’s
desktop. Unlike traditional mainframe and midrange databases, very often the data contained in an
Access database resides on the user’s computer or is only slightly removed by being situated on a
file server on a local area network (LAN). In either case, the valuable data contained in an Access
database can be exposed to potential loss or corruption by well-meaning users.

For example, unless you have added appropriate data validation to the applications you build, it’s
far too easy for a user to enter “bad” data into the database, causing errors later on. Or if you
haven’t applied adequate levels of security to the application, an unauthorized user may acciden-
tally (or intentionally) change sensitive data. At the very least, database security prevents unauthor-
ized users from viewing confidential information. When applied to their fullest, the Access security
features will ensure that valuable data is not accessed by any but the most trusted and reliable
users.

By one definition, bulletproofing an application means applying safeguards to an application’s data
through various techniques and methods. A good way to do this is by making sure that you trap all
errors, preventing crashes and unexpected behavior. This book assumes that you’re already a good
programmer who understands that properly handling errors is a required part of any database
development project.

Cross-Reference
If you aren’t already familiar with handling errors, Chapter 23 explains what is needed to effectively handle the
exceptions that inevitably occur in database applications.


Looking at the Characteristics of


Bulletproofed Applications


Although, as a developer, you want to provide users with maximum flexibility, you simply can’t
allow full access to the entire database environment. Providing users with unrestricted access to
tables, queries, forms, and other database objects, inevitably leads to chaos. Through mischief or
ignorance, changes that damage the database’s structure and logic will most certainly occur. Only
Free download pdf