Is this Chapter Worth Reading Now?

Once again, I will provide three separate overviews ”one for the developer, one for the DBA, and one for the IT manager. I do this because people in each of these categories will approach the chapter in a different way. The developer and the DBA will want to make sure that all but the smallest databases incorporate lessons detailed in this chapter. The IT manager will just want to recognize these practices and raise questions when they are not incorporated.

Overview for the Developer

The AutoExec macro is important because you can open your startup form and additional processes from the one location. If you follow the rules for writing a good AutoExec macro that are detailed in this chapter, you'll find that the macro will be easy to support and enhance.

Splitting a database into front- and back-end databases makes the task of improving an Access database match that of the traditional software development lifecycle. It is also the first step in making your Access front end independent of whether you store your data in an Access database (back end), SQL Server, Oracle, or other. Once you have made the split, you can program the front-end database without impacting the live databases. When the new front end is tested and complete, you can install it by replacing the existing live front end. If you are planning a career in providing contract development by using Access, splitting and relinking databases will be fundamental to your success.

When it comes to error handling, the discussions in this chapter focus on why error handling is an important element of database protection. This element especially applies when you clear the Allow Special Keys option in the Startup dialog. Also discussed are techniques that you can use to locate the source of your errors when you are using the debugger.

Overview for the DBA

The DBA needs to be fully aware of all the macros and VBA code procedures that are run when your database is started. These procedures are important because all the users' activities can be traced back to this point. In this chapter, I discuss a special macro called AutoExec that Access runs whenever anyone opens a database that has that macro in it. From this macro, you can open the main or home form, start any special administration procedures, and maybe even start a background surveillance process to help you administer the database.

After a database is split into a software front end and a data-only back end, the DBA will need to become fully conversant with the issues of table linking. Another consequence of splitting databases is that the DBA will need to know how to replace the front-end software database when the developer makes a new version available.

Overview for the IT Manager

When reading this chapter, an IT manager should be on the lookout for the following:

• A database used regularly by three or more people that has not been split into a software front end and back end. The problem with this scenario is that a developer requires exclusive ownership of the database to make changes to forms and reports , and when this happens, users may not be able to get on with their work.

• A database that has not been split that is being managed by a person in another company or another location. In this scenario, the database may have to be frozen while problems are fixed or objects in the database are modified. Even more worrying in this situation is that all your data may be transferred off-site while the changes are being made.

• Errors that occur on a regular basis. If this starts happening to your database(s), you need to make sure that your users respond in an appropriate manner. If they don't, then you will need to improve the error handling in your database and maybe even reconfigure your user interface to avoid the problems.