Merge pull request #34732 from rwestMSFT/rw-0717-fix-454025

Corrected image for Data conversion article (UUF 454025)

Author: AnnaMHuff

docs/odbc/reference/appendixes/converting-data-from-sql-to-c-data-types.md

@@ -29,7 +29,7 @@ For an ODBC *3.x* application working with an ODBC *2.x* driver, conversion from
 
 The format of the converted data isn't affected by the Windows country/region setting.
 
-:::image type="content" source="media/apd1b.gif" alt-text="Diagram of supported conversions: ODBC C to SQL data types.":::
+:::image type="content" source="media/converting-data-from-sql-to-c-data-types/conversion-table.png" alt-text="Diagram of supported conversions: ODBC C to SQL data types.":::
 
 The tables in the following sections describe how the driver or data source converts data retrieved from the data source; drivers are required to support conversions to all ODBC C data types from the ODBC SQL data types that they support. For a given ODBC SQL data type, the first column of the table lists the legal input values of the *TargetType* argument in `SQLBindCol` and `SQLGetData`. The second column lists the outcomes of a test, often using the *BufferLength* argument specified in `SQLBindCol` or `SQLGetData`, which the driver performs to determine whether it can convert the data. For each outcome, the third and fourth columns list the values placed in the buffers specified by the *TargetValuePtr* and *StrLen_or_IndPtr* arguments specified in `SQLBindCol` or `SQLGetData` after the driver has attempted to convert the data. (The *StrLen_or_IndPtr* argument corresponds to the `SQL_DESC_OCTET_LENGTH_PTR` field of the ARD.) The last column lists the SQLSTATE returned for each outcome by `SQLFetch`, `SQLFetchScroll`, or `SQLGetData`.