Troubleshoot how Access sees your table.
In Access, choose to view the design of your table and ignore messages
about that you will not be able to change things on a linked table. Are
the fields what you think they should be numeric and character.
Does your table have a primary key? It should.
Is the postgres primary key float or int8 or serial8? That would be bad.
Access/ODBC behaves best when your fields are int (int4) or serial
(serial4). There is some indication that adding a timestamp field with
a time of NOW() will allow Access to determine its (client) view of key
matches the Postgres servers view of the key and match records for
updating, etc. -- otherwise you tend to get non-updatable recordsets.
There is some indication that tables that HAVE record OIDs help maintain
the client-server key connection, avoiding the "no current record
problems".
I am a littles surprised at the ability to delete. Access tends to use a
syntax of 'DELETE * FROM table' where Postgres insist on 'DELETE FROM
table' with no *. I have to use pass-throughs to delete records.
I not sure any of this will help but I figure it is worth a shot.
Guy Steven wrote:
>
> I am experiencing a very frustrating problem with postgresql and access
> 2000.
>
> I have a postgresql 7.2.4-5.80 database and am accessing it using access
> 2000.
> Tables are linked using odbc.
>
> I can read a table. I can add records to a table. I can edit and delete
> existing records in the table, but I can not edit or delete records in the
> table that were added using the odbc connection. By this I mean that records
> that are imported into the postgresql (from a dump from pg_dump) can be
> edited or deleted, but if I add a record from access, I can't edit or delete
> from access.
> From within psql the records look identical.
> The error message I get is No Current Record.
>
> Guy Steven
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
