|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer|
The class library provides an exception-handling mechanism based on class CException. The application framework uses exceptions in its code; you can also use them in yours. For more information, see the article Exceptions. You can derive your own exception types from CException.
MFC provides an exception class from which you can derive your own exception as well as exception classes for all of the exceptions it supports.
- The base class for exceptions.
- An archive exception.
- An exception resulting from a failure in a DAO database operation.
- An exception resulting from a failure in ODBC database processing.
- A file-oriented exception.
- An out-of-memory exception.
- An exception resulting from using an unsupported feature.
- An exception resulting from a failure in OLE processing. This class is used by both containers and servers.
- An exception resulting from an error during automation. Automation exceptions are thrown by automation servers and caught by automation clients.
- An exception resulting from a failure to load a Windows resource.
- An exception used to stop a user-initiated operation. Typically, the user has been notified of the problem before this exception is thrown.