Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id B15DB476616 for ; Wed, 14 Aug 2002 19:39:27 -0400 (EDT) Received: from relay02.roc.frontiernet.net (relay02.roc.frontiernet.net [66.133.131.35]) by postgresql.org (Postfix) with ESMTP id E75494763E2 for ; Wed, 14 Aug 2002 19:39:25 -0400 (EDT) Received: (qmail 16751 invoked from network); 14 Aug 2002 23:39:28 -0000 Received: from unknown (HELO there) ([170.215.128.205]) (envelope-sender ) by relay02.roc.frontiernet.net (qmail-ldap-1.03) with SMTP for ; 14 Aug 2002 23:39:28 -0000 Content-Type: text/plain; charset="iso-8859-1" From: terry To: Jean-Luc Lachance , pgsql-interfaces@postgresql.org Subject: Re: BUG: PGACCESS does not warn when trying to update a record that was deleted by someone else. Date: Wed, 14 Aug 2002 20:07:02 -0400 X-Mailer: KMail [version 1.3.2] References: <20020405083629.6a97dcde.dbr@informactis.com> <24205.1018020022@sss.pgh.pa.us> <3D5AD9BF.F127D21A@nsd.ca> In-Reply-To: <3D5AD9BF.F127D21A@nsd.ca> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020814233925.E75494763E2@postgresql.org> X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200208/48 X-Sequence-Number: 3010 Actually, M$ Access does the same thing. When a form (or query) is populated with the contents of a record, it no longer is changed within the database - only within the form (or query). It is only when the record is saved that there is any indication of change or deletion. The only way to determine if the record in the form (or query) has been changed or deleted is to check that record in the database during the operation, which is not routinely done. >> DARN!!! >> >> I have just wasted half a day updating record with PcAccess. >> >> If one is updating a record that was deleted by someone else, >> PgAccess does not warn that the record no longer exists and >> silently accept the update. >> >> Then, if the list is refreshed, the record is gone!!! >> >> ---------------------------(end of >> broadcast)--------------------------- TIP 5: Have you checked >> our extensive FAQ? >> >> http://www.postgresql.org/users-lounge/docs/faq.html -- terry