Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 8C3E2476614 for ; Thu, 15 Aug 2002 12:11:04 -0400 (EDT) Received: from beamish.nsd.ca (unknown [205.150.156.194]) by postgresql.org (Postfix) with ESMTP id C880F4765ED for ; Thu, 15 Aug 2002 12:11:03 -0400 (EDT) Received: (from smap@localhost) by beamish.nsd.ca (8.9.3/8.9.3) id MAA14364; Thu, 15 Aug 2002 12:11:04 -0400 X-Authentication-Warning: beamish.nsd.ca: smap set sender to using -f Received: from reddog.nsd.ca(192.168.101.30) by beamish.nsd.ca via smap (V2.1/2.1+anti-relay+anti-spam) id xma014362; Thu, 15 Aug 02 12:11:02 -0400 Received: from nsd.ca ([192.168.101.148]) by reddog.nsd.ca (8.8.7/8.8.7) with ESMTP id MAA24653; Thu, 15 Aug 2002 12:11:02 -0400 Message-ID: <3D5BD2E4.A7F1F769@nsd.ca> Date: Thu, 15 Aug 2002 12:12:20 -0400 From: Jean-Luc Lachance X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.9-31 i686) X-Accept-Language: en MIME-Version: 1.0 To: terry Cc: pgsql-interfaces@postgresql.org Subject: Re: BUG: PGACCESS does not warn when trying to update a References: <20020405083629.6a97dcde.dbr@informactis.com> <24205.1018020022@sss.pgh.pa.us> <3D5AD9BF.F127D21A@nsd.ca> <200208142339.TAA10893@beamish.nsd.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200208/49 X-Sequence-Number: 3011 But, When a record is updated with PgAccess, the least that it should do is check the return status of the update to find that the record no longer exists and warn the user!!! JLL terry wrote: > > 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