Received: from hub.org.org (localhost [127.0.0.1]) by hub.org (8.10.1/8.10.1) with SMTP id e99NxWJ63629 for ; Mon, 9 Oct 2000 19:59:32 -0400 (EDT) Received: from smtp5s.retemail.es (smtp5s.iddeo.es [62.81.31.74]) by hub.org (8.10.1/8.10.1) with ESMTP id e95HCw793216 for ; Thu, 5 Oct 2000 13:12:58 -0400 (EDT) Received: from celeron ([62.174.96.94]) by smtp5s.retemail.es (InterMail v4.01.01.00 201-229-111) with SMTP id <20001005171524.PKUR25271.smtp5s@celeron> for ; Thu, 5 Oct 2000 19:15:24 +0200 Message-ID: <00cf01c02ef0$4fb0cef0$0d00dcc0@celeron> From: "Erny" To: Subject: Driver or Postgres doesn't report refer. integr. errors Date: Thu, 5 Oct 2000 19:18:21 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00CB_01C02F01.065C9F20" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Archive-Number: 200010/53 X-Sequence-Number: 1410 This is a multi-part message in MIME format. ------=_NextPart_000_00CB_01C02F01.065C9F20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I'm running 7.0 on NT (with cygwin) and ODBC 6.50 I picked up the pgupt.mdb (0.15) to upsize from Access 97. I changed it to use ON UPDATE, ON DELETE ... in the Create statements, disc= arding all the other trigger creations. I'm still early in development, so = I still have not many ideas on the interaction with the drivers. The good news is that all my database with a lot of tables just convert cor= rectly to 7.0 (including the whole referential integrity) and default value= s. Perhaps I will publish soon all the modifications I did on pgupt.mdb After that, I linked all the tables in Access 97 (fast and easy). The bad news, whenever I delete or update a record causing error in refere= ntial integrity, no error is reported to Access. The record seems to disapp= ear, but when rereading the table (or recordset), the 'deleted' record reap= pears. (please send cc to me: aerd@mx3.redestb.es ) Thanx in advance, Erny ------=_NextPart_000_00CB_01C02F01.065C9F20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
I'm running 7.0 on NT (with cygwin) and OD= BC=20 6.50
 
I picked up the pgupt.mdb (0.15) to upsize= from=20 Access 97.
 
I changed it to use ON UPDATE, ON DELETE .= .. in the=20 Create statements, discarding all the other trigger creations. I'm still ea= rly=20 in development, so I still have not many ideas on the interaction with the= =20 drivers.
 
The good news is that all my database with= a lot of=20 tables just convert correctly to 7.0 (including the whole referential integ= rity)=20 and default values. Perhaps I will publish soon all the modifications I did= on=20 pgupt.mdb
 
After that, I linked all the tables in Acc= ess 97=20 (fast and easy).
 
The bad news, whenever I delete or update = a record=20 causing error in referential integrity, no error is reported to Access. The= =20 record seems to disappear, but when rereading the table (or recordset), the= =20 'deleted' record reappears.
 
(please send cc to me: aerd@mx3.redestb.es )
Thanx in advance,
Erny
 
 
 
------=_NextPart_000_00CB_01C02F01.065C9F20--