Re: psqlodbc-08_00_0101 does not work with Ms Access - Mailing list pgsql-odbc

From Andreas
Subject Re: psqlodbc-08_00_0101 does not work with Ms Access
Date
Msg-id 42E4F1B7.2000609@gmx.net
Whole thread Raw
In response to Re: psqlodbc-08_00_0101 does not work with Ms Access  (Zlatko Matić <zlatko.matic1@sb.t-com.hr>)
List pgsql-odbc
Zlatko Matić schrieb:

> several columns! You must use non-floating NUMERICAL field (long) as
> primary
> key. The best is to use autoincrement (BIGSERIAL) field as primary key.
> So, add bigserial fields to all your tables, make them primary keys
> and it
> will solve your problems with "#Deleted".

BIGserials are 8 byte integers.
Access can handle only 4 byte integer fields. The ODBC driver maps the
bigints down to 4 bytes as default setting.
If Access can't actually use the additional 4 bytes why bloat the tables
and add maintenance work to the driver?
It's all fine if your bigserials stay small enough.
Access "Long Integer" are signed and therefore range  from
-2.147.483.648 to 2.147.483.647.
That matches "integer" in PG.







pgsql-odbc by date:

Previous
From: "Joel Fradkin"
Date:
Subject: Re: Blank varchar and text fields
Next
From: Zlatko Matić
Date:
Subject: Re: psqlodbc-08_00_0101 does not work with Ms Access