1) The problem is likely the user name that Access97 is using to communicate
with PostgreSQL. Turn on the logging in the PostgreSQL ODBC driver. Look
at the PostgreSQL log file in your c:\ directory after opening Access97 and
the table in question. Look in the log file and check user name that
PostgreSQL is using to connect to the server and verify that the user exists
in PostgreSQL (including case).
If you are not using Access97 security, then you will need to create an
"Admin" user in postgreSQL. The quotes and uppercase "A" are needed in the
create user statement.
Create user "Admin";
2) Also make sure the user has write permission to the table.
3) Another thing that nailed me was the unique key field. You need to turn
on Unique Key support in the PostgreSQL ODBC driver and each table you want
to update needs to have a unique key installed.
-----Original Message-----From: JT Kirkpatrick [SMTP:jt-kirkpatrick@mpsllc.com]Sent: Friday, April 23, 1999 3:37
PMTo: 'pgsql-interfaces@hub.org'; 'pgsql-admin@hub.org'Subject: [ADMIN] recordset not updateable
I am using rh 5.2, postgres 6.4.2, linking to postgres with access97
and odbc driver. I can create a simple table, link to it, open it, and
access tell me that "this recordset is not updateable". However, I have
created many other tables in the same fashion and even much more complex and
they are just fine. Any idea what could be going on? This just started happening today. Most of the tables I created
overthe past few
weeks are working fine (I met one exception which has led me to create some
test tables and link to them). BTW, I can update the table directly in
psql on the server itself with no problem, so it must be odbc or access.
But why do the other tables still work just fine? HELP!!!! Where can I
look??
JT