Archives of the TeradataForum
Message Posted: Thu, 17 Jul 2003 @ 19:16:10 GMT
Subj: | | Re: 3.02 Teradata ODBC errors |
|
From: | | Kallarakkal, Baburaj (B.) |
Below is something I happened to get from NCR Knowledge base ...This might help...
------
Condition/Symptom:
MS Access Data Type limitations were discovered when testing with MS Access and Teradata ODBC Driver 02.08.02.00 - 03.01.00.XX. Tested MS
Access 97, Access 2000, and XP versions.
Probable Cause:
The following are the MS Access limitations:
1. byte & varbyte
For byte and varbyte datatype columns, we don't get back data through MS Access. Garbage data comes back because MS Access tries to
retrieve all data as "char".
2. date & time
MS Access binds column with Date data type to SQL_C_TIMESTAMP and SQL_TIMESTAMP. See NTA 518 & DR 53717.
3. timestamp with precision > 0
MS Access only supports timestamps with zero precision, retrieval of timestamps greater than zero (0) precision is not possible thru
parameterized query.
4. interval
MS Access does not support this datatype, so when executing parameterized query, Access binds the column SQL_CHAR to SQL_VARCHAR which
results in an error at the Teradata end.
Configuration Data:
Client Platform: All Windows
ODBC Applications: MS Access 97, MS Access 2000, MS Access XP
Teradata ODBC Driver: 02.08.02.XX and higher
Solution:
Be aware of these limitations to avoid the problem.
Regards,
Raj
|