KNOWLEDGE BASE
Log In    |    Knowledge Base    |    4D Home
Tech Tip: Debugging ODBC applications - ignore BADMEM
PRODUCT: 4D | VERSION: 2003.9 | PLATFORM: Win
Published On: July 11, 2007
Your current browser may not allow you to download the asset. We recommend Mozilla Firefox or Google Chrome.
Log In

Tech Tip 46841 suggested using the Tracing feature of the ODBC Data Source Administrator in order to debug ODBC applications. This feature produces a log file that contains a log of all ODBC calls. As part of this log you may notice parameters labeled as "BADMEM". Here is an example:

4D   9a4-9a8   EXIT SQLSetStmtAttr with return code 0 (SQL_SUCCESS)
               SQLHSTMT 01112000
               SQLINTEGER 7 <SQL_ATTR_CONCURRENCY>
               SQLPOINTER 0x00000003 (BADMEM)
               SQLINTEGER 0


It is important to understand that these are not errors. In most cases these are null pointers and, assuming that parameter is optional to the ODBC function in question, are not cause for alarm.