Re: [INTERFACES] Access'97 and ODBC

Thanks to every body that replied my question. Now dates are Ok.

Now I have another problem using M$-Access;
I have a table like this one:

Table = comuni
+------------------------------+----------------------------------+-------+
| Field | Type | Length|
+------------------------------+----------------------------------+-------+
| istat | char() not null | 6 |
| nome | varchar() | 50 |
| provincia | char() | 2 |
| codice_fiscale | char() | 4 |
| cap | char() | 5 |
| regione | char() | 3 |
| distretto | char() | 4 |
+------------------------------+----------------------------------+-------+
... in this table I have stored 8k rows, if I load it from M$-Access and
then I modify a row and I try to save it to database, it goes in a loop
I don't know what's happening.
Please help me. Thanks, Jose'

On Tue, 28 Apr 1998, Hannu Krosing wrote:

> 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