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

From Zlatko Matić
Subject Re: psqlodbc-08_00_0101 does not work with Ms Access
Date
Msg-id 002801c59129$76b2e790$a4748353@zlatkovyfkpgz6
Whole thread Raw
In response to psqlodbc-08_00_0101 does not work with Ms Access  (Christof Thalhofer <devnull@deganius.de>)
List pgsql-odbc
OK..thanks for information. I didn't know that.
Greetings,

Zlatko

----- Original Message -----
From: "Andreas" <maps.on@gmx.net>
To: "Zlatko Matić" <zlatko.matic1@sb.t-com.hr>
Cc: <pgsql-odbc@postgresql.org>
Sent: Monday, July 25, 2005 4:05 PM
Subject: Re: [ODBC] psqlodbc-08_00_0101 does not work with Ms Access


>
> 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.
>
>
>
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
>               http://archives.postgresql.org


pgsql-odbc by date:

Previous
From: Andreas
Date:
Subject: Re: psqlodbc-08_00_0101 does not work with Ms Access
Next
From: Christof Thalhofer
Date:
Subject: Re: psqlodbc-08_00_0101 does not work with Ms Access