This problem still exists in CB 6.1. I just spent several hours trying to find out why records were only rarely not being deleted in my child view when I stumbled on the magic formula: First add a record to the child view, then try to delete a different, older record. Stepping through the code I discovered that IsAddingTB was detecting the previous Add and causing <b>BizObj.Delete</b> to <i>Cancel</i> rather than <i>Delete</i> the current record in the child view.
As Dan pointed out, CT's change to <b>IsAdding</b> fixed the problem with <b>BizObj</b>'s <b>Save</b>, but broke <b>Delete</b>.
<i><font color="#663300">...<snip>...
Attn: Ed
Also, the Delete() method in cBizObj will not work correctly with Table buffered data sets. IsAddingOriginal should be called instead of IsAdding. It would be possible to try and cancel on an old record that you really want to delete.
DAn.
</font></i>
Jim Hansen
Canyon Country Consulting
©2002 James H. Hansen |
