Article View: borland.public.cppbuilder.database.ado
Article #3041Problem with trigger
From: safeline
Date: Fri, 03 Jan 2003 08:21
Date: Fri, 03 Jan 2003 08:21
40 lines
1916 bytes
1916 bytes
Description of the problem's environment: - database SQL Server - a table "Foo1" with a trigger after insert, delete and update; - a table "Foo2" not correlated with "Foo1" ( not foreign key or other ) - the command text in the trigger of table "Foo1" is simply "delete Foo2" - a GUI developped in Borland C++ Builder with ADO objects to access the database - the tables "Foo1" and "Foo2" are accessed by a ADODataSet object - each ADODataSet object have the minimal configuration for access each table ( connection, table name ), all other attributes of the object have default values These are the operations to generate error. Executing a delete method on the ADODataSet pointing to table "Foo1", the operation is correctly executed in the database, but the interface display this message (traslated in English) "Can't find the row selected for the update. It's possible that some values have been modified after last read" or "The key of the row has been modified or deleted from database. Current row will be deleted." remaining in edit mode. Have you a solution?
Technical Details
Message-ID:
<97fd4505.0301030021.47305870@posting.google.com>Path:
arc1-ca.pugleaf.net!archiver1.google.com!postnews1.google.com!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10698b,d5e3b77542400bde,start X-Google-Attributes: gid10698b,public X-Google-ArrivalTime: 2003-01-03 00:21:52 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!postnews1.google.com!not-for-mail From: safelinenews@yahoo.it (safeline) Newsgroups: borland.public.cppbuilder.database.ado Subject: Problem with trigger Date: 3 Jan 2003 00:21:51 -0800 Organization: http://groups.google.com/ Lines: 40 Message-ID: <97fd4505.0301030021.47305870@posting.google.com> NNTP-Posting-Host: 213.188.212.48 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1041582111 13664 127.0.0.1 (3 Jan 2003 08:21:51 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 3 Jan 2003 08:21:51 GMT