I'm not an expert, but I experienced the same troubles with MS
Access/Postgres in the past, so I think I can help you.
I also experienced the trouble with deinstalation of ODBC driver 08_00_0101
and thought that previous versions of drivers are better...
Well, it is not true! You will experience the same "#Deleted" with older
versions of ODBC driver, just leave Access connected to Postgres for two
You can't solve "#Deleted" by installing previous versions of ODBC drivers,
because the problem will remain although you will not realise it so
You can solve it only by modifying your database on Postgres. You must
provide good primary keys to Access.
First of all, don't use varchar(x) primary keys or primary keys combined of
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". The resolution is quite simple.
It definitely solved my problems and my Access aplication works quite good
now, with Postgre 8.0.3 and ODBC driver 08_00_0101.
----- Original Message -----
From: "Christof Thalhofer" <devnull(at)deganius(dot)de>
Sent: Monday, July 18, 2005 7:24 PM
Subject: [ODBC] psqlodbc-08_00_0101 does not work with Ms Access
> first, I want to thank all these people working on Postgresql and Psqlodbc
> in any way for their good job!
> The last weekend, through one day and one night, I found out, that the
> Driver psqlodbc-08_00_0101 does not work correct in conjunction with MS
> Access 97.
> But correct works psqlodbc-07_02_0004!
> My database is running on PostgreSQL 8.0.3/Linux. By using MS Access 97
> with linked tables together with psqlodbc-08_00_0101 these problems occur:
> 1. Tables at Postgresql with a varchar(x) primary key or primary keys
> combined of several columns: If linked in Ms Access 97 all columns are
> marked as "Deleted". Access is not able to use the primary keys.
> 2. Columns in tables in Postgresql with type "text", when linked in Access
> are not recognized correctly as "Memo" by Access. Instead they are
> recognized as "Text" by Access, with a maximum of 255 (or 256?) chars.
> "Text" in Access is the same type as Varchar(256) in Postgresql. "Memo" in
> Access is nearly the same type as "text" or varchar (unlimited) in
> For me it took a long time to figure this out, because whenever i
> deinstalled psqlodbc-08_00_0101, the dlls remained on disk. Several times
> installed an other psqlodbc-driver, but every time in reality psqlodbc-08_
> 00_0101 was used again by Access. I had to delete the psql*.dlls by hand
> be able to reinstall psqlodbc-07_02_0004.
> Because the development is going on, it makes me insecure, that the
> function of psqlodbc was changed in a way that in newer versions it is
> unusable with MS Access.
> Alles Gute and have a good time,
> (For mail change "devnull" to my first name.)
> oans zwoa drei fia
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
In response to
pgsql-odbc by date
|Next:||From: Christof Thalhofer||Date: 2005-07-24 18:07:05|
|Subject: Re: Row versionning between MS-Access and PostgreSQL 8|
|Previous:||From: Zlatko Matić||Date: 2005-07-24 17:35:03|
|Subject: Re: psqlodbc-08_00_0101 does not work with Ms Access|