Postgres Pro
Downloads
Home   >   mailing lists

Thread: ODBC 07.03.0100 Incorrect mapping of Int8 fields in Access

ODBC 07.03.0100 Incorrect mapping of Int8 fields in Access

From
Corrado Cavallini
Date:
ODBC driver version 07.03.0100
PostgreSQL database version 7.3.1

After having updated to the latest I found that I cannot no more read files
containing an Int8 fields in a primary key using Access 2002.
I could still use those files with the legacy driver version.

Is easy to recreate the error:

1)Create a simple table:
CREATE TABLE public._test (
  col1 int8 NOT NULL,
  col2 varchar(50) NOT NULL,
  CONSTRAINT _test_pkey PRIMARY KEY (col1, col2)
) WITH OIDS;
2) manually fill some records
3) open an empty access 2000 database
4) create 2 ODBC DNS using the last and the legacy driver
5) link the table twice, with the two different DNS
6) the table linked with odbc legacy is visible
7) the other give You an error

I have noted that if You look at the design of the linked table, the Int8
column is mapped to "Text 255" while in the legacy is mapped to "Text 19" so
I suspect that the total lenght of the primary key exceed some limit.

Hope this could help

Regards
Corrado Cavallini

Re: ODBC 07.03.0100 Incorrect mapping of Int8 fields in Access

From
Hiroshi Inoue
Date:
Corrado Cavallini wrote:
>
> ODBC driver version 07.03.0100
> PostgreSQL database version 7.3.1
>
> After having updated to the latest I found that I cannot no more read files
> containing an Int8 fields in a primary key using Access 2002.
> I could still use those files with the legacy driver version.
>
> Is easy to recreate the error:
>
> 1)Create a simple table:
> CREATE TABLE public._test (
>   col1 int8 NOT NULL,
>   col2 varchar(50) NOT NULL,
>   CONSTRAINT _test_pkey PRIMARY KEY (col1, col2)
> ) WITH OIDS;
> 2) manually fill some records
> 3) open an empty access 2000 database
> 4) create 2 ODBC DNS using the last and the legacy driver
> 5) link the table twice, with the two different DNS
> 6) the table linked with odbc legacy is visible
> 7) the other give You an error
>
> I have noted that if You look at the design of the linked table, the Int8
> column is mapped to "Text 255" while in the legacy is mapped to "Text 19" so
> I suspect that the total lenght of the primary key exceed some limit.
>
> Hope this could help

Please try the snapshot dll at
    http://www.geocities.jp/inocchichichi/psqlodbc/
or change the *INT8 AS" DSN option.

regards,
Hiroshi Inoue
    http://www.geocities.jp/inocchichichi/psqlodbc/