Received: from sid.trust.ee (root@sid.trust.ee [194.204.23.180]) by hub.org (8.8.8/8.7.5) with ESMTP id KAA17791 for ; Tue, 28 Apr 1998 10:51:04 -0400 (EDT) Received: from sid.trust.ee (wink.trust.ee [194.204.23.184]) by sid.trust.ee (8.8.5/8.8.5) with ESMTP id RAA03513; Tue, 28 Apr 1998 17:49:27 +0300 Message-ID: <3545ECD6.5615904D@sid.trust.ee> Date: Tue, 28 Apr 1998 17:51:02 +0300 From: Hannu Krosing X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: "Jose' Soares Da Silva" CC: pgsql-interfaces@postgreSQL.org, Byron Nikolaidis Subject: Re: [INTERFACES] Access'97 and ODBC References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Jose' Soares Da Silva wrote: > > I have a table with field1 DATE and field2 TIMESTAMP. If I insert data > into these fields, field2 looks OK, but Access97 show me a strange > date on field1. > > This is Access97 output: > field1: 27/7/99 > field2: 1998-04-27 12:20:21+02 > > This is psql output: > Field | Value > -- RECORD 0 -- > field1| 1998-04-27 > field2| 1998-04-27 12:20:21+02 > ---- > PS: My DateStyle is setting to 'ISO' You should set it to 'US' when using Insight ODBC drivers. It should affect the output in no way, but the driver expects it from the backend in US format. As this is a per-connection setting it can safely be set from the driver at startup without affecting other connections. There has been some discussion about 'fixing' it and making the driver recognize other date formats. That would be IMHO unnecessary. It should be enough just to do "SET DateStyle TO 'US';" at startup. This can be currently done by setting some registry entries, but this should really be just a part of driver startup. Hannu