Re: FK Relation
From: Brian Bushay TeamB (BBushay_at_Nmpls.com)
Date: 11/25/04
- Next message: Willi Kühnis: "Re: ADO DBASE Seek"
- Previous message: Brian Bushay TeamB: "Re: FK Relation"
- In reply to: Pepi Nillo: "Re: FK Relation"
- Next in thread: Pepi Nillo: "Re: FK Relation"
- Reply: Pepi Nillo: "Re: FK Relation"
- Reply: Pepi Nillo: "Re: FK Relation"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 24 Nov 2004 22:10:22 -0600
>Yes the detail table has cascading delete too(at database level).
>The database it´s sql server 2000.
>if I do the delete of master table with Access 2000 al work fine.
>The error "cannot find row for update, some values changes from the last
>read" I´m sorry it´s traslate from spanish.
>I use to connect ADO and OLEDB provider for sql server.
Do you have any triggers on the Master table that update the master based on
detail records?
Borland's ADO components use all the fields in the record's selected fields to
find the record to update (in this case) delete. The error you are getting
indicates that when ADO tries to find the record to delete there is not one in
the database with the field values the same as what you have in your
TadoDataset. You could try changing Update Criteria.
ADODataSet1.Properties['Update Criteria'].value :=adCriteriaKey;
You can put this code in the BeforeDelete event. (You need to add ADOInt to
your USE)
This code will force ADO to use just the key field values to locate the record
to be deleted.
Access 2000 may be handling Update criteria this way or it may be using a client
side cursor.
-- Brian Bushay (TeamB) Bbushay@NMPLS.com
- Next message: Willi Kühnis: "Re: ADO DBASE Seek"
- Previous message: Brian Bushay TeamB: "Re: FK Relation"
- In reply to: Pepi Nillo: "Re: FK Relation"
- Next in thread: Pepi Nillo: "Re: FK Relation"
- Reply: Pepi Nillo: "Re: FK Relation"
- Reply: Pepi Nillo: "Re: FK Relation"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|