As I said I'm not an expert...
I wish you to solve your problem on the best possible way.
In my case adding of new colums with bigserial fields as primary keys solved
it. Andreas mentioned that it is not good to use bigserial but just serial,
so I will change it now to serial.
Good luck,
Zlatko
----- Original Message -----
From: "Christof Thalhofer" <devnull@deganius.de>
To: <pgsql-odbc@postgresql.org>
Sent: Sunday, July 24, 2005 11:28 PM
Subject: Re: [ODBC] psqlodbc-08_00_0101 does not work with Ms Access
> Hi Zlatko,
>
> thank you for your reply.
>
>> 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 hours...
>
> we have a couple of Access-Applications running against a 8.03 Postgresql-
> DB. With the old ODBC driver they stay connected the whole day long
> without
> any problems. We also use in some tables varchar(x) primary keys and in
> some other tables primary keys combined of several columns. Without any
> problems for years and with Postgresql 8.xx for months now!
>
> So I stay with my opinion: there are problems with the newer 8.. ODBC
> drivers and Access, which do not occur in older versions, as I described
> in
> my former posting.
>
> Alles Gute,
>
> Christof
> (Für Mail "devnull" in meinen Vornamen ändern.)
>
> --
> oans zwoa drei fia
> #/&wrx§fs$%pff3örx4656tspf&äx=#%xkr§o&(w53x4bl=äh)$˛˛˛˛ł%
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
