Received: from s20.highertech.net (root@s20.highertech.net [209.54.120.20]) by hub.org (8.9.3/8.9.1) with ESMTP id RAA37560; Fri, 23 Apr 1999 17:34:46 -0400 (EDT) (envelope-from jt-kirkpatrick@mpsllc.com) Received: from kirkpatrickjt (whiteoak-34.highertech.net [209.140.56.34] (may be forged)) by s20.highertech.net (8.8.6/8.8.6) with SMTP id RAA19611; Fri, 23 Apr 1999 17:34:36 -0400 Received: by localhost with Microsoft MAPI; Fri, 23 Apr 1999 17:37:06 -0400 Message-ID: <01BE8DAF.E8347DE0.jt-kirkpatrick@mpsllc.com> From: JT Kirkpatrick To: "'pgsql-interfaces@hub.org'" , "'pgsql-admin@hub.org'" Subject: recordset not updateable Date: Fri, 23 Apr 1999 17:37:03 -0400 Organization: MPS, LLC X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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 over the 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