From: | Cedar Cox <cedarc(at)visionforisrael(dot)com> |
---|---|
To: | Evelio Martinez <evelio(dot)martinez(at)testanet(dot)com> |
Cc: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: PostgreSQL ODBC driver: recordset not updatable |
Date: | 2000-12-05 11:21:20 |
Message-ID: | Pine.LNX.4.21.0012051314110.26424-100000@nanu.visionforisrael.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
On Tue, 5 Dec 2000, Evelio Martinez wrote:
> > There are *two* read-only options, did you fix both, and did you re-
> > link your tables after?
>
> yes
>
> > Do you have a primary key for your table?
>
> is it important?. I have a unique key instead of a primary key.
Yes very important. Isn't a primary key the same as a unique key, or just
a key in general? Access has to have a unique field to make sure it
updates the correct record. If Access doesn't recognise a unique field
then it won't let you update the recordset.
What recordset are you trying to update? Is it a linked table or a query?
Also, you must be sure that you relink your tables in Access if you change
something in PG. If you don't, Access will not see the change. You may
want to write some VB code to relink all your tables for you. There is an
example in the Developer Solutions database supplied with Access (you will
also need the Northwind db).
-Cedar
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Mount | 2000-12-05 14:01:39 | RE: JDBC and long TEXT fields |
Previous Message | Andreas Brunner | 2000-12-05 10:12:12 | Error connecting to database |