Free E-Books

These errors are generally a result of
an operation outside the Access environment, and there is no way for Access to handle it. In most
cases, your code won??™t be able to trap and respond to fatal errors. An example of this type of error
is calling a poorly written Windows API function. As you??™ll see in Chapter 30, Windows API functions
are extremely fussy about the type and number of parameters passed to them. Because
Windows API functions execute outside of Access, there is no way for VBA code to trap an API
error. In extreme cases, your users encounter the dreaded blue screen of death often seen when a
computer is infected by a virus.
Because you cannot do much about these fatal errors other than fix them, you should concentrate
on the types of errors you can control.
Simple runtime errors
Runtime errors often give no direct indication of an error condition, such as a pop-up message on a
screen. More likely a runtime error is detected after the fact, when something with the data is discovered
to be erroneous.


Pages:
1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525