Hi Christian, i think the date format of the database doesn't affect the format represented by the odbc-driver. It is in every case internally represented as "YYYY-MM-DD hh:mm:ss" and the represantion in MS Access is an option of the regional settings in the control panel (i think so?! :-).
Greetings Georg JUNG, Christian wrote: >Hi! > >I've got some problems concerning TIME-, DATE- and TIMESTAMP-values: > >First of all: How does the DB-parameter "DATE_TIME_FORMAT" affect the way >those values are displayed and/or saved (e.g. via SQLStudio, ODBC, JDBC). > >How does SAP DB save the date/time-values internally? > >What settings should I use when connecting to the SAP DB via ODBC from >Windows and JDBC? > >I've got some problems with SAP DB 7.3.0.21 (and previous releases) running >under Linux, the newest ODBC-driver for Windows and Access2k. A table with a >TIMESTAMP-field and a FIXED(18,4)-field returns the following error-message: >"[SAP AG][...]Datetime field overflow;-3050 POS(1) Invalid timestamp >format:ISO.(#-3050)" when I try to open it under Access2k. > >The table has following content (reported by SQLStudio using SQLMode >INTERNAL): > > A | B > ---------------------|------------- > 25.04.2002 16:02:40 | 1 > 25.04.2002 16:02:48 | 2 > 25.04.2002 16:02:53 | 3 > 29.04.2002 15:59:39 | 4 > >Changing the DB-parameter "DATE_TIME_FORMAT" to "EUR" or "ISO" doesn't >affect the behaviour of Access. > >What am I doing wrong? Thanks for your help! > > >Regards >Christian Jung > >PS: You'll find a zipped sqltrace of a Access2k-session with the sapdb and >my test-table as attachment. > web www.iee.lu _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
