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

Re: New libpq based driver snapshot 08.01.0003 available

From: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
To: "Cris Carampa" <cris119(at)operamail(dot)com>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: New libpq based driver snapshot 08.01.0003 available
Date: 2005-08-15 11:55:33
Message-ID: 6EE64EF3AB31D5448D0007DD34EEB3417DD0AD@Herge.rcsinc.local (view raw or flat)
Thread:
Lists: pgsql-odbc
> I rebooted the machine, installed 7.03.02.00 and relinked the tables.
> 
> I still have the "#Deleted" problem. The problem seem to occour only
> with tables where a varchar(255) column is part of the primary key.
> 
> In another table all the cells are filled with label "#Error", the
> problem seem to be a decimal truncation or something like that.
> 
> These problems seem to be related with MSAccess 2000, a colleague of
> mine with Access97 doesn't seem to face this problems.
> 
> I will try to investigate these problems further and if I find
someting
> interesting I will let you know.
> 
> Thank you. Kind regards,

Probably access has some kind of key limitation.  Another way of getting
this problem is using high precision timestamps inside the primary key
since access can't deal with them on the clientside.

Good luck, AFAIK there is no solution to this problem except to work
around it.  It is more a limitation of access than anything else.

Merlin

pgsql-odbc by date

Next:From: Ben TrewernDate: 2005-08-15 12:43:52
Subject: Re: Bug or not about ASCII and Multi-Byte character set
Previous:From: CHENDate: 2005-08-15 09:53:12
Subject: re:psqlodbc-08_00_0102 and LATIN1 database

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