ODBC: Calling ODBC API Functions Directly
The new home for Visual Studio documentation is Visual Studio 2017 Documentation on docs.microsoft.com.
The latest version of this topic can be found at ODBC: Calling ODBC API Functions Directly.
The database classes provide a simpler interface to a data source than does ODBC. As a result, the classes do not encapsulate all the ODBC API. For any functionality that falls outside the abilities of the classes, you must call ODBC API functions directly. For example, you must call the ODBC catalog functions (::SQLColumns, ::SQLProcedures, ::SQLTables, and others) directly.
Note
ODBC data sources are accessible through the MFC ODBC classes, as described in this topic, or through the MFC Data Access Object (DAO) classes.
To call an ODBC API function directly, you must take the same steps you would take if you were making the calls without the framework. They steps are:
Allocate storage for any results the call returns.
Pass an ODBC HDBC or HSTMT handle, depending on the parameter signature of the function. Use the AFXGetHENV macro to retrieve the ODBC handle.
Member variables CDatabase::m_hdbc and CRecordset::m_hstmt are available so that you do not need to allocate and initialize these yourself.
Perhaps call additional ODBC functions to prepare for or follow up the main call.
Deallocate storage when you finish.
For more information about these steps, see the Open Database Connectivity (ODBC) SDK in the MSDN documentation.
In addition to these steps, you need to take extra steps to check function return values, ensure that your program is not waiting for an asynchronous call to finish, and so on. You can simplify these last steps by using the AFX_SQL_ASYNC and AFX_SQL_SYNC macros. For more information, see Macros and Globals in the MFC Reference.