| **Navigation:**  SQL Drivers > ODBC Accelerator Driver >====== ODBC Data Types ====== | [[how odbc works.htm|{{btn_prev_n.gif|Previous page}}]][[coming future.htm|{{btn_home_n.gif|Return to chapter overview}}]][[sseia.htm|{{btn_next_n.gif|Next page}}]] |
|  ||

{{c6h0067.jpg|C6H0067.jpg}}

**Notes:**

| C | The Clarion data type can be used to manipulate the ODBC data type. CREATE does create the ODBC data type. |
| • | The Clarion type can be used to manipulate the ODBC data type, however, CREATE does NOT create the ODBC data type. |
| 1 | Clarion LONG, SHORT, and BYTE can be used with ODBC DECIMAL and NUMERIC data types if the ODBC field does not have any decimal places. |
| 2 | ODBC TIMESTAMP fields can be manipulated using a STRING(8) followed by a GROUP over it which contains only a DATE field and a TIME field. |

**Example:**

**  TimeStampField STRING(8),NAME('TimeStampField')**

**  TimeStampGroup GROUP,OVER(TimeStampField)**

**  TimeStampDate   DATE**

**  TimeStampTime   TIME**

**                 END**

CREATE creates a TIMESTAMP field if you use a similar structure.

| 3 | Some loss of precision may occur. |
| 4 | Rounding errors may occur. |
| 5 | CREATE attempts to create a TINYINT for a BYTE. If the backend does not support TINYINT, CREATE treats BYTE as a SHORT. CREATE attempts to create a SMALLINT for a SHORT. If the backend does not support SMALLINT, CREATE treats SHORT as a LONG. CREATE attempts to create an INTEGER for a LONG. If the backend does not support INTEGER, CREATE creates a decimal field. |

{{notebox.jpg|NoteBox.jpg}}

**Your backend database may contain data types that are not listed here. These data types are converted to ODBC data types by the backend database. Consult your backend database documentation to determine which ODBC data type is used.**