Re: psqlodbc-08_00_0101 does not work with Ms Access

From: Andreas <maps(dot)on(at)gmx(dot)net>
To: Zlatko Matić <zlatko(dot)matic1(at)sb(dot)t-com(dot)hr>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: psqlodbc-08_00_0101 does not work with Ms Access
Date: 2005-07-25 14:05:43
Message-ID: 42E4F1B7.2000609@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Zlatko Matić 2005-07-25 14:58:56 Re: psqlodbc-08_00_0101 does not work with Ms Access
Previous Message Joel Fradkin 2005-07-25 13:25:16 Re: Blank varchar and text fields