|
Free Resources from FMS |
|
|
|
|
"Thank you! Thank you! I just finished reading this document, which was part of a link in the recent Buzz newsletter. I have printed it for others to read, especially those skeptical on the powers of Access and its capabilities." - Darren D. |
|
|
|
|
Microsoft
Access Resource Center
Microsoft Access Error Number and Error Description Reference
by Luke Chung, President of FMS, Inc.
Introduction to Error Codes
When an error occurs in your Microsoft Access application, Access provides an error number and description.
If you have error handling in place, the error object (Err) lets you get the error number (Err.Number) and description (Err.Description). For instance, Error 11 is for "Division by zero".
If you are building applications for international use, you should only rely on the error number because the error description is localized to the language of the Access installation.
List of Error Numbers and Descriptions
As a resource and reference guide, we've tabulated all the Access error codes from Microsoft Access 2007, 2003, 2002/XP, and 2000.
There are lots of error numbers. Two lists are available:
Error Numbers and Descriptions for Microsoft Access 2007
This is the list of the 2,687 Error IDs and Error Descriptions for Microsoft Access 2007:
HTML Format (717K)
Microsoft Access 2007 Error Number and Descriptions
110 page PDF Report (732 K)
Comparison of Error Descriptions among Microsoft Access 2007 through 2000
This is the entire list of Error IDs and Error Descriptions for Microsoft Access 2007, 2003, 2002/XP, and 2000. Identical error descriptions are hidden so you see the Access 2007 ones, plus any changes over time. Knowing this can be helpful if your users report a different error description from what you expected based on the version of Access they are running.
227 page PDF Report (1.2 MB)
Additional Resources
Read our whitepaper on Microsoft Access Error Handling and Debugging for related information on making your Access database applications more robust and professional.
Here's a Microsoft KnowledgeBase Article (142138) which describes how to address some of the errors: An Explanation of Trappable Errors in Visual Basic for Apps. Their explanation for error 49 is not complete. Read our article on Bad DLL Calling Convention instead.
