ClientDataSet with SQL Server Triggers
From: Mark A. Deal (nospam_at_idaknow.com)
Date: 06/22/04
- Next message: Brian Bushay TeamB: "Re: SQL Server uniqueindentifier field"
- Previous message: Bob Fleischman: "SQL Server uniqueindentifier field"
- Next in thread: Brian Bushay TeamB: "Re: ClientDataSet with SQL Server Triggers"
- Reply: Brian Bushay TeamB: "Re: ClientDataSet with SQL Server Triggers"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 21 Jun 2004 20:07:34 -0400
I have triggers setup on my SQL Server database which handle cascading
deletes. I am using ClientDataSets in my D7E application and when I attempt
to delete a record I get an error back from the server explaining that it
cannot locate the records for deletion.
My assumption is that the TClientDataSet is handling the deletions properly
and then the SQL Server trigger fires and the records are no longer there to
delete.
Anybody know of a way around this quandary?
Assume that I have very little control over the triggers or, better yet,
would prefer to use the internal trigger-based RI provided by triggers.
Sure would appreciate any thoughts or advise.
-- Mark A. Deal Document & Data Solutions, LLC http://www.docsol.com Time Matters AIC HotDocs Certified Consultant GhostFill Certified Consultant
- Next message: Brian Bushay TeamB: "Re: SQL Server uniqueindentifier field"
- Previous message: Bob Fleischman: "SQL Server uniqueindentifier field"
- Next in thread: Brian Bushay TeamB: "Re: ClientDataSet with SQL Server Triggers"
- Reply: Brian Bushay TeamB: "Re: ClientDataSet with SQL Server Triggers"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|