DIFFERENT WAYS OF USING ERROR HANDLING

There are many ways to use error handling to your benefit. For example, by using error handling, you can account for situations that can't be debugged at development time. These are just a few situations that can occur during runtime and can be handled by using Access's error-handling commands:

The user has forgotten to place the disk in the floppy drive, causing an error. You can have the system prompt the user to place the disk in the drive and then try again.

The user is deleting some tables from the database through code, but one of the tables is already deleted. This normally causes an error. In some cases you might not care, so you can have the error handler continue with the next line in the code.

When someone moves the back end (the database on the server) to another location on the network, you can test for it when starting up the application. To do so, you need to turn off error handling and trap the error yourself. If a particular error has occurred, you can call a routine to relink the tables.