How To Determine Visual Basic Trappable Errors (136250)


The information in this article applies to:

  • Microsoft Visual Basic Standard Edition, 32-bit, for Windows 4.0
  • Microsoft Visual Basic Professional Edition, 16-bit, for Windows 4.0
  • Microsoft Visual Basic Professional Edition, 32-bit, for Windows 4.0
  • Microsoft Visual Basic Enterprise Edition, 16-bit, for Windows 4.0
  • Microsoft Visual Basic Enterprise Edition, 32-bit, for Windows 4.0
  • Microsoft Visual Basic Learning Edition for Windows 5.0
  • Microsoft Visual Basic Learning Edition for Windows 6.0
  • Microsoft Visual Basic Professional Edition for Windows 5.0
  • Microsoft Visual Basic Professional Edition for Windows 6.0
  • Microsoft Visual Basic Enterprise Edition for Windows 5.0
  • Microsoft Visual Basic Enterprise Edition for Windows 6.0
This article was previously published under Q136250

SUMMARY

This article demonstrates how you can determine if an error you are receiving from a Visual Basic program is a Visual Basic trappable error or if it coming from another source.

MORE INFORMATION

When you run Visual Basic, follow these steps to get more information on a specific error:
  1. Stop your program if it is currently running.
  2. Press the F8 key to go from design mode to break mode.
  3. Press CTRL+G to activate the debug window.
  4. Enter the following statement and wait for the error message to appear:

    Error <error-number> For example, type Error 70 and the following error message appears:
    Run-time error '70':
    Permission denied
  5. Press the F1 key to get information from online Help on that specific error.

    For example, in Visual Basic 4.0, pressing F1 on Error 70 displays the Permission denied (Error 70) page from Visual Basic Help.

    In Visual Basic 6.0, pressing F1 on Error 70 displays the Permission denied (Error 70) page from the Visual Basic for Applications Reference.
If the error description is: Application-defined or object-defined error, then the error number does not correspond to an error defined by Visual Basic for Applications (VBA). Such errors may be defined by the host application (for example, Microsoft Excel or Visual Basic), but if you want to generate them from code, you must use the Raise method, and fill in all relevant arguments.

REFERENCES

The Visual Basic 6.0 Reference Documentation has a section on Trappable Errors. This section includes documentation on the core Visual Basic language errors, miscellaneous Visual Basic errors, OLE Container Control errors, RDO errors, and ActiveX Control errors.

For additional information on trappable errors for Visual Basic 3.0, click the article number below to view the article in the Microsoft Knowledge Base:

108340 How To Determine Visual Basic 3.0 Trappable Errors

Modification Type:MinorLast Reviewed:7/1/2004
Keywords:kbDocs kbhowto kbref KB136250
©2004 Microsoft Corporation. All rights reserved.