Received: from olympus.scw.org (IDENT:root@209-9-156-98.sdsl.cais.net [209.9.156.98]) by hub.org (8.10.1/8.10.1) with ESMTP id e72ICjG32721 for ; Wed, 2 Aug 2000 14:12:45 -0400 (EDT) Received: from hades (hades.scw.org [209.9.156.99]) by olympus.scw.org (8.9.3/8.8.7) with ESMTP id OAA25594; Wed, 2 Aug 2000 14:17:39 -0400 From: "Joel Burton" Organization: Support Center of Washington To: "Simon Hardingham" Date: Wed, 2 Aug 2000 14:17:37 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: ODBC, Access and updates/deletes alter 0 rows! CC: pgsql-interfaces@postgresql.org Message-ID: <39882D81.5378.90A4FB6@localhost> In-reply-to: <4DCB16536FCBD311897000A0C92A02ED19FB11@sauron.netxtra.net> X-mailer: Pegasus Mail for Win32 (v3.12c) X-Archive-Number: 200008/24 Can you post a script that will create a table with some data? This will help debug the problem? On 2 Aug 2000, at 18:08, Simon Hardingham wrote: > Hi, > > I have been using the Postgres ODBC driver to connect from Access 97 & > 2000 clients to postgres 6.5.3 running on Redhat 6.2 without any sort > of problems. We have just finished upgrading to 7.0.2 and also > updated to the latest ODBC driver, 6.50. > > Since then though we are having trouble making changes to fields from > Access, ie. UPDATEs and DELETE's. Some tables seem to work fine, > maybe limited to those which do not have many rows or fields. > However, generally there is an update error suggesting that someone > else has modified the data, with options to copy to clip-board etc. > With the ODBC logging switched on I can take the SQL it is generating > and paste this into psql and run it. This will always say that o rows > have been updated or deleted. > > For all these queries the WHERE clause details the value for each of > the fields in the table for that particular table. Is there a limit > on the length of a query, although these seem to vary in length quite > a lot. I can normally get it to work by removing certain of the > fields from the where clause, seems to work best if I remove the > clauses which are referring to float4 fields, but again may just be > coincidence. > > I have looked all over the documentation for some explanation and > changed all the ODBC driver parameters, but can't get it work > reliably. I can supply much more information such as table layouts, > queries, sizes, platform etc if required but I am not too sure where > to go from here and so what might be relevant. If anyone can offer > any help I can supply this. > > Thanks for any help provide and I hope I can get my screaming users > back to work and happy again soon. > > Thanks > > Simon > > > _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ > _/ Simon Hardingham - netXtra Ltd - UK _/ > _/ Tel: +44 (0) 1787 319393 Fax: +44 (0) 1787 319394 _/ > _/ http://www.netxtra.co.uk simon@netxtra.co.uk _/ > _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ -- Joel Burton, Director of Information Systems -*- jburton@scw.org Support Center of Washington (www.scw.org)