Hi Christian
> -----Original Message-----
> From: JUNG, Christian [mailto:[EMAIL PROTECTED]]
[snip]
> And here we go again! Now I've got a detailed description of
> my problem. In
> short: MS Access 2000 version 9.0.3821 SR-1 does not display
> a table, which
> contains a TIMESTAMP-column and which is a primary key.
>
> Here's what I'm doing:
[very accurate and helpful description snipped]
I investigated the problem and found out that Access binds a wrong
parameter type by reading the primary key.
Excert from the driver manager trace:
:
MSACCESS a54-888 EXIT SQLBindParameter with return code 0
(SQL_SUCCESS)
HSTMT 08E42470
UWORD 1
SWORD 1 <SQL_PARAM_INPUT>
SWORD 99 <SQL_C_DEFAULT>
SWORD 10 <SQL_TIME>
<<<<<<<<<<<<<<<<<
SQLULEN 26
SWORD 0
PTR 0x0012C1F8
SQLLEN 0
SQLLEN * 0x0012C1F4 (16)
MSACCESS a54-888 ENTER SQLExecute
HSTMT 08E42470
MSACCESS a54-888 EXIT SQLExecute with return code -1 (SQL_ERROR)
HSTMT 08E42470
DIAG [22008] [SAP AG][SQLOD32 DLL][SAP DB]Datetime field
overflow;-3050 POS(1) Invalid timestamp format:ISO. (-3050)
:
It says it binds SQL_TIME but provides a time stamp value. Considering the
date as
time the driver responds with datetime overflow, since the year 2002 is
mapped to hours
where the allowed range is 0-23 (see ODBC reference). If the driver wouldn't
notice,
I guess, some random values would be filled into the time part of time
stamp.
Maybe this is, what you saw with MySQL.
To confirm this, I defined a table like yours with time instead of time
stamp.
This time the binding is ok and the link worked fine.
Maybe the MS support is able to provide a fix for Access.
Regards Thomas
----------------------------------------------
Dr. Thomas K�tter
SAP DB, SAP Labs Berlin
SAP DB is open source. Get it! www.sapdb.org
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
