Received: from mail.fpsn.net (mail.fpsn.net [63.224.69.57]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0R1QYq73365 for ; Fri, 26 Jan 2001 20:26:34 -0500 (EST) (envelope-from cfaber@fpsn.net) Received: from fpsn.net (control.fpsn.net [63.224.69.60]) by mail.fpsn.net (8.9.3/8.9.3) with ESMTP id SAA80369 for ; Fri, 26 Jan 2001 18:26:26 -0700 (MST) (envelope-from cfaber@fpsn.net) Message-ID: <3A72236A.D4507F2C@fpsn.net> Date: Fri, 26 Jan 2001 18:24:58 -0700 From: Colin Faber Reply-To: cfaber@fpsn.net Organization: fpsn.net, Inc. X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 CC: pgsql-sql@postgresql.org Subject: Re: #DELETED error when using Access 2000 as frontend References: <3A71E144.26096.EC47B9E@localhost> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200101/406 X-Sequence-Number: 1082 these are common errors on the mysql side also. Most likely poor planing on the Access end. Emils Klotins wrote: > > > I want to use pg 7.x as a backend for a MS Access application. I linked a > > > table via ODBC, using the newest ODBC driver. I can open and view tables. But > > > after I insert a new record, all fields will contain "#deleted". When I > > > reopen the table, the inserted data is displayed correctly. > > I recall seeing an MS Access 2000 bug that will cause this. I don't remember > I can confirm the problem exists at least in access'97 -- applying > both of the office'97 service packs helped. > > I have noticed all kinds of weird errors in Access which makes it > operate badly with Postgres and I really can't recommend it as a > frontend application, although I know there are people who use it > quite successfully. > > On a side note - pls reply privately - what Win frontends (apart from > web) have people used with Postgres, which work OK for them? > > Emils > > ---------------------- > Emils Klotins > IT Manager, Baltic states > Grafton Entertainment Ltd. / TVNET > 40-43 Brivibas Str., Riga LV1050, Latvia > +371-7-242-001