Watch, Follow, &
Connect with Us
Public Report
Report From: Delphi-BCB/Midas/TClientDataSet    [ Add a report in this area ]  
Report #:  3777   Status: Closed
InternalCalc fields are reset to null by ApplyUpdates when using poPropogateChanges
Project:  Delphi Build #:  6.240
Version:    7.0 Submitted By:   Dave Rowntree
Report Type:  Basic functionality failure Date Reported:  3/12/2003 3:20:39 AM
Severity:    Commonly encountered problem Last Updated: 10/6/2006 6:50:55 AM
Platform:    95, 98, 2000, NT, XP Internal Tracking #:   157212
Resolution: Fixed (Resolution Comments) Resolved in Build: : 7.0.8.1
Duplicate of:  None
Voting and Rating
Overall Rating: (2 Total Ratings)
5.00 out of 5
Total Votes: 2
Description
The InternalCalc fields are reset to null by CDS.ApplyUpdates if DSP poPropogateChanges is true and there is a change made to a field in the DSP.BeforeUpdateRecord/DSP.AfterUpdateRecord events.

Having poPropogateChanges = True without actually making a change to a field in BeforeUpdateRecord/AfterUpdateRecord events does not reset the InternalCalc fields.

This problem also occurs in D7.
Steps to Reproduce:
1. Download the test case app from the Attachments tab.

2. Compile and run the test case app.

3. Follow the on screen steps.
Workarounds
None
Attachment
3777.zip
Comments

Dave Rowntree at 3/12/2003 3:26:19 AM -
Would someone confirm that this problem exists in D7 please.

wayne hubbard at 3/12/2003 6:36:33 AM -
sorry, i should have mentioned in our NG thread.  I *am* using D7.
it definitely fails there.  -pal

Dave Rowntree at 3/12/2003 1:17:21 PM -
wayne hubbard said - "sorry, i should have mentioned in our NG thread.  I *am* using D7.
it definitely fails there.  -pal"


Thanks.

Chee Yang Chau at 9/13/2003 8:22:34 AM -
I confirmed this bug happen in D7 as well.  However, it has another side effect in addition to previous comments.  The ChangeCount of the main clientdataset won't reset to 0 after the ApplyUpdates call.  The ChangeCount should always reset to 0 if a ApplyUpdates is executed successfully.

Dave Rowntree at 5/11/2004 5:13:08 AM -
Different problem See QC#2333

Dave Rowntree at 5/11/2004 3:28:13 AM -
Fixed in Midas.dll

Server Response from: CODE1