Skip site navigation (1) Skip section navigation (2)

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

From: Zlatko Matić <zlatko(dot)matic1(at)sb(dot)t-com(dot)hr>
To: "Andreas" <maps(dot)on(at)gmx(dot)net>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: psqlodbc-08_00_0101 does not work with Ms Access
Date: 2005-07-25 14:58:56
Message-ID: 002801c59129$76b2e790$a4748353@zlatkovyfkpgz6 (view raw or flat)
Thread:
Lists: pgsql-odbc
OK..thanks for information. I didn't know that.
Greetings,

Zlatko

----- Original Message ----- 
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>
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 


In response to

pgsql-odbc by date

Next:From: Zlatko MatićDate: 2005-07-25 18:41:39
Subject: Re: psqlodbc-08_00_0101 does not work with Ms Access
Previous:From: AndreasDate: 2005-07-25 14:05:43
Subject: Re: psqlodbc-08_00_0101 does not work with Ms Access

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group